Bring your own OAuth app
A bring your own OAuth app means social accounts connect through credentials your organization owns, while managed infrastructure covers callbacks, the authorization-code exchange, encrypted token storage, token refresh, and publishing. During authorization, the provider consent screen presents your product name and branding. You retain responsibility for provider review, quota, and credentials, without operating a separate OAuth backend.
Your app, managed OAuth infrastructure
Start by registering an app directly with a social platform. Enter the callback URL there, then record the resulting client ID and client secret in your project. At connection time, select that saved app rather than a managed one. The authorization experience then displays your product identity on the provider consent screen. Behind the scenes, managed infrastructure still receives the callback, performs the authorization-code exchange, keeps tokens in encrypted token storage, runs token refresh, and handles publishing. You gain ownership of the provider relationship while avoiding a second OAuth system to run.
When BYOK is useful
A customer-owned app makes sense when identity, ownership, or isolation is a requirement. Examples include showing your logo during authorization, being accountable for platform review and compliance, keeping quota separate for your application, running distinct apps for separate products or customers, or keeping credentials inside your organization. When none of those needs are present, a managed app is simpler. Publishing behaves identically in both cases, so the choice is about ownership and branding rather than publishing capability. Use the decision checklist below before creating a provider app.
One saved app, many connections
Credentials are stored at project level, so one registration can serve several accounts on the same platform. Later maintenance includes renaming the saved app, swapping its icon, or rotating credentials. Each connection keeps a record of the app that produced its tokens. That record is what allows managed and customer-owned connections to exist together in one project without overwriting each other.
Supported platforms
The platforms covered by this approach are X, YouTube, LinkedIn, Pinterest, TikTok, Instagram, Facebook, Threads, and Google Business Profile. Bluesky follows a different model, relying on per-user app passwords. Providers also differ in product names, permission sets, review processes, and vocabulary, so platform-specific guidance should take precedence over any generic sequence.
Set up your first app
Begin by creating an app for the selected platform and entering the callback URL supplied by the managed service. Save the client ID and client secret in your project. After saving, begin a new account connection and choose the saved app before selecting the platform. The sequence below adds a check at each stage, including confirming that the consent screen displays the correct branding before finishing.
| Condition | Use your own app? | Why it matters |
|---|---|---|
| Your product name and logo must appear on the authorization screen | Yes | The provider consent screen shows your app's branding instead of the managed app's. |
| Your organization must own platform review and compliance | Yes | The provider relationship, review status, and compliance obligations sit with your app. |
| Provider quota must be isolated to your application | Yes | Usage and limits are tied to your own provider app rather than a shared managed app. |
| Separate apps are needed for different products or customers | Yes | Each saved app can be selected per connection, keeping products and customers separate. |
| Credentials must remain under your organization's control | Yes | Your team owns the client ID and client secret and can rotate the client secret. |
| None of the above applies | No — use a managed app | Managed apps require no extra setup and use the same publishing interface. |
Decision aid based on the conditions described in the source; platform-specific review and quota rules vary by provider.
| Field | Where it is set | Required? | Notes |
|---|---|---|---|
| Platform | When creating the saved app | Yes | Choose one supported platform per saved app. |
| Callback URL | In the provider app you create with the social platform | Yes | Add the callback URL provided by your managed service; the managed service handles the callback. |
| Client ID | Saved once in your project after provider setup | Yes | Stored with the saved app and reused across connections for that platform. |
| Client secret | Saved once in your project after provider setup | Yes | Stored with the saved app; you can rotate its client secret later. |
| Display name and icon | Saved app settings | Optional | Rename the saved app or change its icon after saving. |
| OAuth app selection | Per connection, at connect time | Yes | Each connection remembers which OAuth app issued its tokens. |
Field map derived from the source's described inputs; requiredness labels are editorial guidance, not a source API schema. No literal callback URL value was supplied, so none is shown.
| Step | Action | Failure check |
|---|---|---|
| 1. Create the provider app | Create an app with the social platform and add the callback URL provided by your managed service. | Confirm the callback URL was entered in the provider app before saving credentials. |
| 2. Save the credentials | Store the client ID and client secret once in your project for that platform. | Confirm both values are present in the saved app before starting a connection. |
| 3. Start a connection | Return to integrations, start a new connection, and select your OAuth app before choosing the platform. | Confirm the provider consent screen shows your app's name and branding, not the managed app's. |
| 4. Verify token handling | Complete the connection and confirm publishing works for the connected account. | Confirm the connection completes; token refresh should keep the connection working over time. |
Worked sequence based on the source's described flow; platform-specific provider steps are not detailed here. Checks are general guidance, not source-stated error behavior.
| Scenario | What happens | How to handle it |
|---|---|---|
| Bluesky connection attempted with a customer-owned OAuth app | Bluesky uses per-user app passwords instead of a customer-owned OAuth app, so this approach does not apply. | Use the per-user app password flow for Bluesky instead. |
| Client secret rotated in the provider app | The saved app still holds the previous client secret until you update it. | Rotate its client secret in the saved app settings so the saved app matches the provider app. |
| Saved app renamed or icon changed | The saved app's display details change; existing connections keep the OAuth app that issued their tokens. | Rename or change the icon in saved app settings. |
| Managed and customer-owned connections in one project | Each connection remembers which OAuth app issued its tokens, so both types coexist. | Select the intended OAuth app per connection at connect time and verify the consent screen branding before completing. |
| Consent screen shows the wrong branding | The connection was started with the managed app instead of your saved app. | Restart the connection and select your OAuth app before choosing the platform. |
Edge cases drawn from the source's described behavior; provider-specific errors and review outcomes are not specified in the source.
Frequently asked questions
When should I bring my own OAuth app instead of using a managed app?
Choose a customer-owned app when branding on the consent screen, ownership of review and compliance, isolated provider quota, separate apps per product or customer, or organization-controlled credentials are requirements. Without those requirements, a managed app needs less setup and publishing works the same way.
Can one saved app be used for many social accounts?
Store credentials once for a platform, then reuse that saved app across several accounts on that platform. Every connection records the app behind its tokens, allowing managed and customer-owned connections to sit side by side. Display details can change later, and you can rotate its client secret.
Which platforms support a customer-owned OAuth app, and what is the exception?
Bluesky does not fit this model because access there relies on per-user app passwords rather than a customer-owned OAuth app. X, YouTube, LinkedIn, Pinterest, TikTok, Instagram, Facebook, Threads, and Google Business Profile are the platforms covered here.
What are the basic setup steps?
Register an app with the chosen social platform, enter the callback URL supplied by the managed service, then save the resulting client ID and client secret. During account connection, pick the saved app so the consent screen displays your product identity.
What does the managed service still handle if I use my own app?
Callbacks, the authorization-code exchange, encrypted token storage, token refresh, and publishing remain managed. Your team remains responsible for the provider app, including its credentials, branding, review status, and quota relationship.