better-i18n.com
Developer DocsHelp CenterChangelog

Register Your App

On this page

How registration works #

OAuth applications are registered by the Better i18n team during partner onboarding. We create the application record in our database with your app's details and send you back a client_id.

What we need from you #

FieldDescription
App nameWhat users see on the consent screen
Icon URLSquare PNG or SVG, ≥ 64×64 (optional but recommended)
Redirect URIsWhere we send users after authorization. Byte-for-byte match required at exchange time. HTTPS required in production; http://localhost is allowed for development. Send the full list (prod + every dev port).
Application typeweb (server-side), native (desktop/mobile), or spa (browser-only). All types use PKCE; the field is informational only.

What you'll receive #

  • A client_id — your app's unique identifier
  • A client_secret — a secret key your server uses during token exchange and refresh

What you'll need on your side #

  • A redirect URI endpoint (e.g., https://yourapp.com/oauth/callback)
  • A backend to handle the callback and store client_secret, refresh_token, and grant_id securely
  • Your client_secret available as an environment variable (e.g., BETTER_I18N_CLIENT_SECRET)

Dynamic Client Registration (advanced) #

If your platform programmatically provisions integrations, we support RFC 7591 Dynamic Client Registration at:

Code
POST https://api.better-i18n.com/api/auth/mcp/register

This endpoint is rate-limited and requires prior arrangement. Contact us if you need automated registration.

Next step #

Once you have a client_id, start the authorization flow.