Bring your own credentials

Many OAuth connectors come with Scalekit’s own OAuth app credentials, so you can create a connection and test it without registering an app with the provider. The connection form offers Use Scalekit credentials when a connector supports it. Connectors without Scalekit credentials need your own OAuth app from the start, as described in Configure connections.

You can go live on Scalekit’s credentials. Your users then see Scalekit’s name and branding on the consent screen, not yours.

Bring your own credentials lets you replace Scalekit’s shared OAuth credentials with your own. Once configured, users see your app name, logo, and terms on every OAuth consent screen.

What changes when you use your own credentials

• Consent screens display your application’s name and branding
• Rate limits and quotas are tied to your OAuth app, not Scalekit’s shared pool
• Provider relationship is direct, and your OAuth app appears in provider dashboards and audit logs
• Compliance: useful if your organization requires a direct relationship with each OAuth provider

Nothing changes in your code or the Scalekit SDK. The switch is purely a dashboard configuration on the connection.

Configure your credentials

1. Copy the redirect URI from Scalekit

   Go to AgentKit > Connections and click Edit on the connection you want to update. Select Use your own credentials. The form expands and displays a Redirect URI. Copy it.

2. Register your OAuth app with the provider

   In the provider’s developer console, create a new OAuth app (or use an existing one). Add the Redirect URI you copied in the previous step to the list of authorized redirect URIs.

   Redirect URI must match exactly

   The URI must match character-for-character. A mismatch will cause OAuth flows to fail with a redirect_uri_mismatch error.

   The provider gives you a Client ID and Client Secret after registration.

   Many provider consoles create the app in an internal or development mode by default. That works for your own testing but is not sufficient for customer consent.

3. Enter your credentials and save

   Back in Scalekit Dashboard, enter the Client ID and Client Secret from your OAuth app and click Save.

   All new OAuth flows for this connection will now use your credentials.

   Saving credentials only wires your app into Scalekit. Before customers can connect, promote the app to allow external accounts and validate it end-to-end — see the AgentKit launch checklist.

Existing connected accounts

Existing connected accounts are not affected immediately

Switching credentials does not re-authorize users who are already active. They continue using the previous credentials until they re-authorize. If you need all users to see your branding immediately, generate new authorization links and prompt them to re-authorize.