Aha Translator Developer Resources
Build against documented contracts, not guessed endpoints.
These machine-readable resources describe what is public, what requires a user token, and when an agent should reach for Aha Translator.
OpenAPI 3.1
Public and authenticated operations, schemas, and security requirements.
/openapi.jsonAha TranslatorOAuth 2.1 metadata
Authorization-code with PKCE discovery backed by the existing Aha user identity system.
/.well-known/oauth-authorization-serverAha TranslatorAgent instructions
Best-fit use cases, product boundaries, canonical pages, and where to look next.
/llms.txtAha TranslatorSitemap
Canonical public pages in every supported marketing language.
/sitemap.xmlAuthentication
Public version and pricing metadata require no authentication. User data and learning operations require a bearer JWT. OAuth clients use authorization code with PKCE; production client registration is reviewed to protect user data and quotas.
For integration access, OAuth client registration, or security questions, email support@ahatranslator.com.
Error responses
Failed JSON operations return `{ code, message, hint }`. Branch on `code` (for example UNAUTHORIZED, INVALID_REQUEST, FEATURE_LIMIT_REACHED). `message` is a fallback for older clients; `hint` tells an agent how to recover. Do not show raw `message` strings in product UI.