AccelByte Matchmaking API
Matchmaking V2 pools and tickets.
AccelByte Matchmaking API is one of 13 APIs that AccelByte publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Matchmaking. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against 2 base URLs: https://demo.accelbyte.io, https://{namespace}.accelbyte.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
AccelByte Matchmaking API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
It accepts HTTP basic authentication (basicAuth).
By default, every request must be authenticated.
bearerAuth— OAuth2 access token issued by the IAM token endpoint.basicAuth— OAuth2 client id / client secret used at the token endpoint.
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 1 DELETE, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Matchmaking V2 pools and tickets.
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are MatchTicketRequest (4 properties), MatchTicket (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from AccelByte 12
Other APIs AccelByte publishes across the network.