rlink:start

This is an old revision of the document!


WorldsEdgeLink API

Rate Limits and Access Patterns - The game API has rate limits of approximately 200 requests per minute - Rate limit violations trigger a 429 HTTP error - Recommended configuration: Implement a throttler at 100 requests per 30 seconds for safety

- Safe to access:

  1. Ongoing games
  2. Match histories
  3. Leaderboards

Use a dual-API approach: 1. Game API

  1. Primary use: Fetching ongoing observable games
  2. Expected usage: 10-15 requests per minute

2. Community API

  1. Use for match histories and leaderboards
  2. Benefits from higher rate limits
  3. Reduces load on main game API

- Accessing chat channels - Accessing presence-related features - Making POST requests - Creating lobbies via API - Any other write operations

Implement logging for rate limit errors (HTTP 429) to monitor API usage patterns

https://aoe.ms/replay/?gameId=<game_id>&profileId=<profile_id>

Example request

parameter type value comments
gameIdint64156900198
profileIdint642858362

Where <profile_id> is the perspective of the recorded game. Basically from which client it was uploaded. Matters for view lock.

Some stuff is zlib-compressed. E.g. inside

slotinfo

there's a

metaData

field that seem to be a two-pass base64 string holding binary data Couldn't deduce options yet. It's zlib as well, but the uncompressed string looks different, it's not base64(?)

  • rlink/start.1738452849.txt.gz
  • Last modified: 15 months ago
  • by nimda