Skip to main content

Endpoint

Overview

Quarantine pauses an account: it stays exactly as it is, but no scheduled post is dispatched for it. Use it when the platform has blocked the account — a human-verification prompt, a signed-out session, content strikes — so its scheduled posts stop failing while the block is unresolved. Nothing is torn down and no post is lost. Posts remain scheduled and become eligible again the moment the account is released. Releasing restores the status the account held before it was quarantined.

Request Body

string
required
Account to quarantine or release
string
required
Either "quarantine" or "release"
string
Why the account is being quarantined. Required when action is "quarantine"; stored on the account and shown to whoever resolves it.

Response

string
The account that was updated
string
"quarantined" after quarantining, or the restored prior status after release
string
Echo of the reason recorded (quarantine only)
boolean
Present and true when the account was already quarantined — the call is safe to repeat
boolean
Present and true after a successful release

Example

Response Example

Notes

  • Quarantining is idempotent — repeating it returns alreadyQuarantined: true rather than overwriting the original reason.
  • Releasing an account that is not quarantined returns 400.
  • A key restricted to the account:quarantine scope may call this endpoint; a key bound to specific accounts may only act on those. See Restricted Keys.