Disconnect an account
Removes the caller's account-level credential and every grant, cached reachability answer, and stored secret that belonged to it. The workspace install the credential was mirrored from is disabled and stripped of its copy of the token, and its Google push channels are stopped, so Snoze stops syncing and receiving data for the account immediately. Automations pinned to it are paused rather than silently re-run under a different identity.
apiKeyAuthorizationBearer <snoze_sk_…>Workspace API key created in Workspace settings → API keys. Scopes on the key bound what it can read and write.
accountId*stringSuccess
application/json- response
data*curl -X DELETE 'https://api.snoze.dev/v1/me/connected-accounts/string'{ "data": { "id": "string" }}What breaks if I disconnect this account
Lists the automations pinned to this credential that will pause, and how many shared resources the caller will stop being able to reach, so a disconnect names its consequences before it happens.
Resolve shared resources for this viewer
Answers, for the signed-in viewer only, whether each referenced external resource is reachable through one of their own credentials. Never resolves through the credential of whoever placed the reference. At most 50 distinct refs per request (the payload accepts up to 400 ids before de-duplication); more is a validation error, not a truncated answer. Answers are cached per viewer and per satisfying account, positively for ten minutes and negatively for two so newly granted access appears quickly; `forceRecheck` clears the cached answers first. A probe that errors or exceeds five seconds renders as no access rather than falling back to another credential. A redacted ref the viewer cannot reach carries no name, URL or provider id.