Disconnect a social account
Disconnects one account in the caller's own Zernio account and drops it from the stored list. An account that is not on the caller's profile answers the same 404 as one that does not exist. Zernio keeps its own record of the disconnect and bills the freed slot accordingly.
Disconnects one account in the caller's own Zernio account and drops it from the stored list. An account that is not on the caller's profile answers the same 404 as one that does not exist. Zernio keeps its own record of the disconnect and bills the freed slot accordingly.
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 account id.
Response Body
application/json
application/json
application/json
curl -X DELETE "https://example.com/social/accounts/string"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.
List your posts and scheduled queue GET
Returns the caller's posts, newest first: drafts awaiting approval, the scheduled queue, and posts already published or failed. Each entry carries the per-platform text the Publish page previews, the putty asset ids, and an `approveUrl` for a draft.