Matchmaker limitations

Review the key limitations and rate limits that apply to the Matchmaker service.

Matchmaker has several restrictions on configuration properties and settings to help you design and optimize your integration.

Rate limits

The Matchmaker service uses rate limits to help control network traffic by restricting the number of requests received by the API within any given second.

The following table shows the rate limit for each Matchmaker service request for Players and Service Accounts:

Request typePlayer auth rate limitService account rate limit
Create ticket1 request per second66,000 requests per second
Get ticket status1 request per second660,000 requests per second
Delete ticket1 request per second66,000 requests per second
Create backfill ticketN/A1 request per second
Update backfill ticketN/A1 request per second

Matchmaker requests limitations

Ticket creation requests are limited to 25 KB.

The matchmaking ticket properties have the following size limitations:

Ticket propertyLength limit
Player ID64 characters
Number of players100 or the maximum number of players in a team
Number of custom data properties128
Custom Data property name64 characters
Custom Data string propterty200 characters
Custom Data array size100 items

Queue and pool limitations

The limit for queues is 10. The limit for pools is 10 pools per queue.

Matchmaking configuration

The following table shows the matchmaking configuration limits:

Configuration propertiesLength Limit
Teams100
Team rules25
Match rules25
Relaxations per rule25