openapi: 3.1.0 info: title: Aghanim Server-to-Server Achievements Locales API description: "The Aghanim Server-to-Server API is designed for **backend server integrations only**. Use this API when you need to automate game hub updates from your server-side applications.\n\n\n## OpenAPI Specification\n\nYou can download the [OpenAPI](https://www.openapis.org/) specification for this API at the following link:\n[docs.aghanim.com/openapi.json](https://docs.aghanim.com/openapi.json).\n\n## Changelog\n\nSee the [S2S API Changelog](https://docs.aghanim.com/s2s-api/changelog/) for a history of changes to this API.\n\n## Authentication\n\nAghanim supports two methods of authentication: **Bearer token** and **Basic authentication**.\n\nTo authenticate, you will need your API key, which can be retrieved from\nthe Aghanim Dashboard → [**Game → Integration → API Keys**](https://dashboard.aghanim.com/go/integration/api-keys).\n\n**⚠️ Security Notice**: The S2S API key is **secret** and must be kept secure on your server. Never expose the S2S API key in client-side code, mobile apps, or any public-facing applications.\n\n### Bearer Token Authentication\n\nUse the Bearer method by including an `Authorization` header with the word `Bearer`\nfollowed by your API key. The `Authorization` header in your HTTP request should look like this: `Authorization: Bearer API_KEY`\n\n### Basic Authentication\n\nAlternatively, you can authenticate using Basic authentication. Your API key is used\nas the `username`, and the `password` should be left empty. Send an `Authorization`\nheader with the word `Basic` followed by a base64-encoded string\nin the format `API_KEY:` (note the colon at the end).\n\nThe `Authorization` header should look like this: `Authorization: Basic ZGVtbzpwQDU1dzByZA==`\n\n## Error Codes\n\nAghanim employs standard HTTP response codes to denote the success or failure of an API request.\nBelow is a table detailing error codes.\n\n| Code | Description |\n| ---- | ----------- |\n| 200 | OK |\n| 400 | Bad request |\n| 401 | Not authenticated |\n| 403 | Not authorized |\n| 404 | Resource not found |\n| 409 | Conflict. Request conflicts with current state of resource |\n| 422 | Validation error |\n| 429 | Too many requests. Rate limit exceeded |\n| 503 | Server unavailable |\n\n### Generic error schema\n\n```json\n{\n \"detail\": \"string\"\n}\n```\n\n### Validation error schema\n\n```json\n{\n \"detail\": [\n {\n \"loc\": [\n \"string\",\n 0\n ],\n \"msg\": \"string\",\n \"type\": \"string\"\n }\n ]\n}\n```\n\n## Rate Limits\n\nThe Aghanim API has rate limiting in place to avoid overloading and to ensure it remains stable.\nThe allowable rate of requests is capped at 1,000 per minute for every game.\nGame developers who exceed this limit will receive a 429 error code.\n\nTo increase the rate limit, please contact us via [integration@aghanim.com](mailto:integration@aghanim.com).\n\n## Pagination\n\nIn the Aghanim API, pagination is managed through the use of the `limit` and `offset` query parameters.\nThese parameters allow to fine-tune your data retrieval requests by specifying:\n\n- `limit`: the number of records to be returned in a single request.\n- `offset`: indicates the number of records to skip from the start of the dataset.\n" contact: name: Aghanim email: integration@aghanim.com version: 2026.07.14 servers: - url: https://api.aghanim.com/s2s description: Production tags: - name: Locales paths: /v1/locales: get: tags: - Locales summary: Get Locales description: Returns a list of locales. operationId: get_locales security: - HTTPBearer: [] parameters: - name: limit in: query required: false schema: title: Limit description: A limit on the number of objects to be returned default: 10 type: integer description: A limit on the number of objects to be returned - name: offset in: query required: false schema: title: Offset description: The number of objects to skip type: integer description: The number of objects to skip responses: '200': description: Successful Response content: application/json: schema: type: array items: $ref: '#/components/schemas/LocaleRead' title: Response Get Locales '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' post: tags: - Locales summary: Create Locale description: Creates a new locale. operationId: create_locale security: - HTTPBearer: [] requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/LocaleCreate' responses: '201': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/LocaleRead' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' /v1/locales/{locale_id}: get: tags: - Locales summary: Get Locale description: Returns a single locale. operationId: get_locale security: - HTTPBearer: [] parameters: - name: locale_id in: path required: true schema: title: Locale Id type: string responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/LocaleRead' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' put: tags: - Locales summary: Update Locale description: Updates a locale. operationId: update_locale security: - HTTPBearer: [] parameters: - name: locale_id in: path required: true schema: title: Locale Id type: string requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/LocaleUpdate' responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/LocaleRead' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' delete: tags: - Locales summary: Delete Locale description: Deletes a locale. operationId: delete_locale security: - HTTPBearer: [] parameters: - name: locale_id in: path required: true schema: title: Locale Id type: string responses: '204': description: Successful Response '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' components: schemas: Locale: type: string enum: - cs - de - en - es - fr - fr-CA - hi - id - it - ja - ko - ms - nl - 'no' - pl - pt - pt-BR - ru - sv - th - tr - uk - vi - zh - zh-Hant title: Locale description: Language codes according to ISO 639-1. LocaleRead: properties: locale: $ref: '#/components/schemas/Locale' published_at: title: Published At type: integer id: type: string maxLength: 32 title: Id stats: $ref: '#/components/schemas/LocaleStats' status: $ref: '#/components/schemas/LocaleStatus' modified_at: title: Modified At type: integer type: object required: - locale - id - stats - status title: LocaleRead LocaleUpdate: properties: {} type: object title: LocaleUpdate ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError LocaleStats: properties: total: type: integer title: Total default: 0 done: type: integer title: Done default: 0 type: object title: LocaleStats LocaleStatus: type: string enum: - clean - translating - synchronization - fuzzy title: LocaleStatus LocaleCreate: properties: locale: $ref: '#/components/schemas/Locale' published_at: title: Published At type: integer type: object required: - locale title: LocaleCreate HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError securitySchemes: HTTPBearer: type: http scheme: bearer description: Refer to the [Authentication](https://docs.aghanim.com/api-reference/) section for instructions on obtaining an API key and use it as the `Bearer` token.