Provider credentials (developers)
For hosted account connection instructions, start with Connect accounts. You do not need your own developer app for ordinary hosted OAuth connections.
Use these pages when you need your own provider credentials for the SDK, local CLI accounts, or the self-hosted REST server. If you only use the hosted Scheduler, connect accounts in the Scheduler UI and come back here only when a provider asks for an app, redirect URI, scope, board, page, or token detail.
Local CLI OAuth connections use your own provider developer app. If you do not want to manage provider credentials, connect the CLI or an MCP client to the hosted Scheduler instead. The "Cheapest path" column reflects that.
| Platform | Setup time | Main credential | Cheapest path | Guide |
|---|---|---|---|---|
| Bluesky | 2 min | App password or OAuth tokens | App password, or Scheduler | Bluesky |
| Telegram | 2–3 min | Bot token and chat ID | CLI with --bot-token | Telegram |
| X | 5 min + paid X API access | OAuth 2.0 user tokens | Scheduler, or your own X app | X |
| 5–10 min | Page access token | Scheduler, or your own Meta app | ||
| 10–15 min | Meta page token and IG business account ID | Scheduler, or your own Meta app | ||
| 10–15 min | OAuth access token and member/page ID | Hosted Scheduler, or your own LinkedIn app | ||
| 10–15 min | OAuth access token and board ID | Hosted Scheduler, or your own Pinterest app | ||
| Threads | 10–15 min | Threads access token and user ID | Hosted Scheduler, or your own Meta app | Threads |
| TikTok | 20–30 min | TikTok access token | Hosted Scheduler, or your own TikTok app | TikTok |
| YouTube | 20–30 min | Google OAuth refresh token | Scheduler, or your own Google app | YouTube |
For the trade-offs between Scheduler connections, your own OAuth app, env vars, and accounts.json, see credential strategies.
Provider dashboards change often. If a label differs from the wording you see in the provider portal, look for the equivalent setting: app permissions, redirect URI, OAuth scopes, account/page/channel selector, and token generation.
Core also supports DEV/Forem when enabled in a deployment. It is not part of the current ten-platform hosted offering.