Register Your App
Get a client_id to start integrating with Better i18n OAuth 2.0.
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.
Self-service registration is coming soon. For now, reach out to us at [email protected] or through your existing contact to get started.
What we need from you
| Field | Description |
|---|---|
| App name | What users see on the consent screen |
| Icon URL | Square PNG or SVG, ≥ 64×64 (optional but recommended) |
| Redirect URIs | Where we send users after authorization. HTTPS required in production; http://localhost is allowed for development |
| Application type | web (server-side), native (desktop/mobile), or spa (browser-only) |
What you'll receive
- A
client_id— your app's unique identifier - No
client_secretfornative/spatypes — they use PKCE exclusively - For
webtype, aclient_secretif your auth scheme requires it
What you'll need on your side
- A server-side backend to handle the OAuth callback and store tokens securely
- A redirect URI endpoint (e.g.,
https://yourapp.com/oauth/callback)
Local development: Include http://localhost:3000/oauth/callback (or your dev port) in your redirect URIs. We allow HTTP without TLS for localhost.
Dynamic Client Registration (advanced)
If your platform programmatically provisions integrations, we support RFC 7591 Dynamic Client Registration at:
POST https://api.better-i18n.com/api/auth/mcp/registerThis 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.