The Rankedin Public API lets your organization read selected Rankedin data programmatically — for example to check on your own website whether a player holds an active license, or to see which teams in your Team League have paid their fees.
Access is granted per organization through an API key.
Generate your API key
You need to be an admin of a club or organization in Rankedin.
- Go to Organization Manager → your organization → Settings.
- Scroll to the last section, Public API, and open it.
- Click Generate API Key.
Once generated, the section shows:
| Control | What it does |
|---|---|
| API Key | Your key, hidden by default. |
| Show | Reveals the full key. |
| Copy | Copies the full key to your clipboard. |
| Status | ACTIVE (usable) or revoked (no longer works). |
| Created | When the key was generated. |
| Last used | When the key was last used in a request, or Never. |
| Regenerate API Key | Creates a new key. The old one stops working immediately. |
| Revoke/Disable API Key | Switches the key off immediately. You can generate a new one right away. |
| Request log activity | Shows recent request activity for your key. |
Treat the key like a password
Anyone who has it can read your organization's data through the API. Share it only with trusted systems — never in public code, e-mails or screenshots. If you suspect it has leaked, click Regenerate API Key.
There is one active key per organization. Regenerating or revoking takes effect immediately, so every integration using the old key stops working at once. Remember to update your systems.
Call the API from your server, never from the browser
Your website must call the Rankedin API from its backend. If you put the API key into JavaScript running in the visitor's browser, every visitor can read it and use your organization's key.
The correct pattern for a member zone is:
visitor's browser → your own server (holds the API key) → Rankedin API
The API deliberately does not allow browser-to-Rankedin calls from other websites, so a front-end-only integration will not work.
Rankedin IDs
Most endpoints identify people and teams by their Rankedin ID, a 10-character code shown on any Rankedin profile.
| Type | Example | Used by |
|---|---|---|
| Player | R000006081 | Player endpoints |
| Team | T000105100 | Team name lookup |
| Organization | 803 | Organization endpoint |
| Team League | 14245 | Team League endpoint |
Keep the leading zeros
Always treat a Rankedin ID as text, not a number — the leading zeros are part of the ID and must not be stripped. Organization and Team League IDs, on the other hand, are plain numbers.
What your key can and cannot see
- License checks and Team League data are limited to your own organization. A player who is not a member of your organization is not returned, and a Team League that is not yours returns 403 Forbidden.
- Name lookups are public. The organization, player and team name endpoints return the same name shown on the Rankedin website, so they also work for records outside your own organization.
- The API exposes no personal data beyond what each endpoint documents. The license check in particular returns no name, e-mail, phone or club.
Error responses
Every error returns an HTTP status code and a JSON body in the same shape:
{
"type": "https://httpstatuses.com/401",
"title": "API key is required.",
"status": 401,
"detail": "The request could not be authenticated.",
"code": "api_key_missing",
"traceId": "0HNNT34M179LL:00000011"
}Use code in your integration — it is stable. Quote traceId when contacting Rankedin support.
| Status | Meaning | What to do |
|---|---|---|
| 400 | The ID or request body is not in the expected format | Check the format rules for the endpoint |
| 401 | Key missing, empty, malformed, unknown, or sent more than once | Send exactly one valid X-API-Key header. If the key was revoked, generate a new one |
| 403 | The Team League does not belong to your organization | Use an ID that belongs to your organization |
| 404 | Organization, player or team does not exist | Verify the ID |
| 409 | More than one record matches the requested Rankedin ID | Contact Rankedin support |
| 429 | You hit the rate limit | Wait and retry, ideally with increasing delays |
| 500 | Unexpected error on our side | Retry later; contact support with the traceId |
| 503 | Key validation is temporarily unavailable | Retry after a short pause |