Skip to main content
The public API is read-only and requires an API key tied to a Rankly server or bot.

Base URL

Authentication

Send your API key in the X-API-Key header.
You can also provide the key as ?key=..., but the header is the preferred form.

Response shape

Most endpoints return a standard envelope:
Errors return:

Endpoints at a glance

GET /server

Returns the server metadata for the API key owner.

Example response

GET /bot

Returns the bot metadata for the API key owner.

Example response

GET /votes/:userId

Checks whether a user can vote again right now.

Path parameters

Example response

The cooldown window is 12 hours.

GET /reviews

Returns reviews for the authenticated server.

Query parameters

Example response

Example client code

Error handling

  • 401 means the key is missing or invalid.
  • 400 means the endpoint does not match the key type or the parameter is invalid.
  • 429 means the request limit was exceeded.
  • 500 means the backend hit an unexpected error.

Best practices

  • Keep the API key on your server.
  • Cache responses that do not need to change every second.
  • Use /votes/:userId only when you need the live cooldown state.
  • Prefer the public API reference over reverse-engineering dashboard calls.