Start connecting a social account
Asks Zernio for an OAuth URL for one platform and returns it. The dashboard opens `authUrl` in a new tab; Zernio redirects back to `/social/connect/callback` with `connected`, `profileId`, `accountId` and `username` appended. The platform slugs are Zernio's own: `facebook`, `instagram`, `linkedin`, `twitter`, `tiktok`, `youtube`, `threads`, `reddit`, `pinterest`, `bluesky`, `googlebusiness`, `telegram`, `snapchat`, `discord`, `slack`, `whatsapp`.
Asks Zernio for an OAuth URL for one platform and returns it. The dashboard opens authUrl in a new tab; Zernio redirects back to /social/connect/callback with connected, profileId, accountId and username appended. The platform slugs are Zernio's own: facebook, instagram, linkedin, twitter, tiktok, youtube, threads, reddit, pinterest, bluesky, googlebusiness, telegram, snapchat, discord, slack, whatsapp.
Authorization
bearerAuth A bearer token. The Account routes accept a Privy access token; the MCP transport accepts an sk- API key issued by POST /account/api-keys.
In: header
Path Parameters
Zernio's platform slug to connect.
Request Body
application/json
The connect request body. Omit the body entirely to use the default profile.
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/social/connect/string" \ -H "Content-Type: application/json" \ -d '{}'{ "authUrl": "string", "profileId": "string"}List your connected social accounts GET
Returns the social accounts connected in the caller's own Zernio account, read live through the caller's own stored key. putty holds no Zernio account of its own and pays nothing: every connected account is billed to the user's Zernio account. When the account has several Zernio profiles and the user has not chosen one, `profileCandidates` is non-null and the Integrations page renders a picker from it; with one profile it is used automatically, and with none putty creates one named "putty".
Zernio's OAuth redirect target GET
Where Zernio sends the browser after a connect. On success it appends `connected`, `profileId`, `accountId` and `username`; the route records the account on the caller's profile and redirects to the dashboard. On failure it appends `error` and `platform` (plus optional `error_message`, `is_user_fixable`, `reason`, `dashboard_url`, `missing_scopes`, `error_reason`, `platform_error*`). **This route is public**: it is Zernio's server, not the user's browser, that follows the redirect, and there is no session on that request. The caller's identity comes from the `state` Zernio echoed back from the connect URL, and the account id is scoped to the caller's own Zernio profile, so a forged callback can only ever write an account onto the profile whose key created it.