Multiplayer Operations

The Multiplayer Operations Developer Hub

Welcome to the Multiplayer Operations developer hub. You'll find comprehensive guides and documentation to help you start working with Multiplayer Operations as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    API Reference

Protocol

The base protocol for clients to access zeuz is JSON-over-HTTP.

Error in request handling are reported back using standard HTTP status codes. For details see Error handling.

Requests

All APIs use one of the three URL forms

  • <<API_ENDPOINT_URL>>/API_NAME
  • <<API_ENDPOINT_URL>>/PROJECT_ID/API_NAME
  • <<API_ENDPOINT_URL>>/PROJECT_ID/ENVIRONMENT_ID/API_NAME

Please see Scopes for details.

All API names use only lowercase ASCII letters, digits and the underscore character '_'

All host names, IDs and API names are case sensitive.

Every request needs to have the following fields:

Field

Type

Description

Session

SessionID

The ID of an authenticated session or an empty string before authentication.

Time

Timestamp

The server-side time in zeuz is time integer format.

ReqId

string

A random client-assigned request ID. This should never be reused.

SignHash

string

The cryptographic signature for the request header data. See details.

Data

object

The API-specific request payload

Responses

Every response follows this format:

Field

Type

Description

Time

Timestamp

The server-side time in zeuz is time integer format.

Error

string

A specific error message if an error occured.

Data

object

The response payload.

Updated 5 months ago


Protocol


The base protocol for clients to access zeuz is JSON-over-HTTP.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.