A user can end a connection from either side: through your app, or from inside Instagram,
Threads, X or LinkedIn. Both paths end with the stored credentials gone.
From your app
DELETE /api/v1/accounts/:id disconnects an account and deletes its stored tokens.The account stops appearing in GET /api/v1/accounts immediately, and any later publish
targeting it answers 404 account_not_found.
From the platform
When someone removes Chirio in their Instagram or Threads settings, Meta notifies Chirio and
the affected accounts and their tokens are deleted automatically. Nothing is required from
you.
An account can disappear without you asking
Because platform-side revocation is silent from your perspective, an accountId you hold can stop being valid at any time. Handle 404 account_not_found on publish as 'ask the user to reconnect' rather than as a bug.
For X and LinkedIn, a revocation surfaces the next time the credentials are used: the account
moves to expired or revoked and publishing to it fails that target with
account_not_active. See Account lifecycle.
Data deletion requests
Meta requires a route for users who ask for their data to be deleted rather than merely
disconnected. Chirio handles those requests inline — the accounts and tokens for that platform
user are removed, and the user receives a confirmation code and a status page they can check.Requests arriving this way are verified as genuinely coming from the platform before anything
is deleted.
What is kept
Deleting or revoking an account removes the connection and its credentials. It does not delete
the post history already recorded under your project — those records are what your own
audit trail and billing rest on, and they no longer contain anything that can act on the
user's behalf.If you need post history deleted as well, that is a support request rather than an API call.
