Connect players to their next match.

Use your game’s supported matching criteria to bring players or groups together. Define the experience around the rules and constraints your matchmaking integration supports.
Tickets/queues
Available matching criteria
Results and cancellation
Contextual draft · Release status, supported versions, and limits await owner review.

Plan the integration

Tickets/queues

Define when a player enters a queue and how the client displays waiting or cancellation.

Available matching criteria

Choose attributes your matching rules actually support, such as game mode or group size.

Results and cancellation

Handle a matching result and coordinate the separate connection to your game session.
ILLUSTRATIVE GAME WORKFLOW

group players by a supported game-mode attribute.

This example describes a game-team workflow. Service connections and game rules require explicit integration; it does not imply automatic bindings.

Scope and responsibilities

Matching players is separate from allocating and hosting servers. Define ticket cancellation and the handoff into your game session.

Related services

Explore complementary services for your game, with integration details for each building block.
SERVICE 1

Parties

Keep the group together as they play. Explore Parties
SERVICE 2

Lobbies

Give players a shared place before the match. Explore Lobbies

Setup prerequisites

A test workspace with access to Matchmaking.
Step 1: pending
A confirmed API version and documented permissions for the workflow.
Step 2: pending
Client and backend tests for successful, invalid, repeated, and interrupted requests.
Step 3: pending
Review integration availability →
YOUR NEXT CHAPTER STARTS HERE

Build the backend for your next game.

Explore the services and plan your first player experience.