Skip to content

Bring your own OAuth app

Bring your own OAuth app, often shortened to BYOK, means publishing through provider applications that carry your branding rather than a shared one. The service still runs the OAuth callback, exchanges authorization codes, keeps tokens in encrypted token storage, refreshes them, and publishes on your behalf. You register the application in the provider's own developer console and hand over its client ID and client secret. This path suits teams that want their identity on the consent screen, usage counted against their own provider quota, or direct responsibility for provider review and compliance.

When to bring your own OAuth app

Bring your own OAuth app when you need your name and icon on the consent screen, your own provider quota, or direct control over Provider approval. You maintain the application in the platform’s developer console. The service handles the OAuth callback, code/token exchange, encrypted token storage, refresh tokens and publishing.

Create the app, then connect accounts

  1. Follow the relevant platform guide and configure its callback.
  2. Open Integrations → Apps (BYOK) → New app, choose the platform, and enter its client ID and client secret. Select Create app.
  3. Open Integrations → Integrations → New integration. Select your saved OAuth app before choosing its platform and authorizing an account.

Bluesky uses per-user app passwords, so it has no customer-owned OAuth app guide in this list.

Prepare for provider review

Prepare the app’s identity and public website, privacy policy and terms, a clear account-data usage explanation, development credentials, and a demonstration recording of connection and publication. Exercise the flow with development users before requesting production access. A working test-user connection does not by itself authorize general customer access.

Manage credentials and active connections

From Apps (BYOK), you can change an app’s name or icon and rotate its stored client secret. The platform and client ID stay fixed because issued refresh tokens belong to that client ID. Switching client IDs requires a separate app and fresh authorization for the affected accounts. Before deleting an app, remove each active integration by disconnecting it or reconnecting it elsewhere.

Use BYOK through the API

Create an app with POST /v1/apps/. Pass its returned app.id as appId to GET /v1/connect/{platform} when requesting an OAuth URL. Use the Apps API reference for app fields and the Connect guide for account authorization..

Platform guides and the Bluesky exception
PlatformSetup guide
X (Twitter)Configure an X OAuth app
YouTubeConfigure a YouTube OAuth app
LinkedInConfigure a LinkedIn OAuth app
PinterestConfigure a Pinterest OAuth app
TikTokConfigure a TikTok OAuth app
InstagramConfigure an Instagram OAuth app
FacebookConfigure a Facebook OAuth app
ThreadsConfigure a Threads OAuth app
Google Business ProfileConfigure a Google Business Profile OAuth app
BlueskyNot listed: uses per-user app passwords instead of a customer-owned OAuth app

Platform list preserved from the supplied source; per-platform callback URLs, scopes, and review requirements were not in the supplied text and are not stated here.