admin

Record clearance of a legacy revoke_failed account

Updates legacy revoke_failed rows to revoked. A confirmed upstream kill also clears the account's leak marker; declining confirmation preserves it. Reconnect does not wait for this clearance. The route refuses a live revoke debt and does not reactivate an account. Internal admin users only.

post/v1/admin/integrations/accounts/{account_id}/revoke-failure-clearances

Request

  • Base URL: https://api.patricia.app (the document declares no server; this is the origin it was published from)
  • URL: https://api.patricia.app/v1/admin/integrations/accounts/{account_id}/revoke-failure-clearances
  • Auth: HTTP bearer

Path parameters

account_idstring uuid required

Connected account with the legacy revoke_failed status.

Request body

upstream_confirmed_revokedboolean required

True when the operator verified in the provider's own console that the credential is gone. False when they are accepting a leak they could not kill — the account then stays on the orphan report, because it may still be billing.

Response

Successful Response

accountstring required
tenant_idstring required
clearedboolean required

False when the clearance did not take; see refusal for why.

refusal'not_revoke_failed' | 'live_debt_exists'

Why a revoke-failure clearance did not take. DERIVED at the point of refusal, never stored.

This route clears a legacy revoke_failed row, with or without a confirmed kill; reconnect does not wait for it.

  • NOT_REVOKE_FAILED: the row does not carry the legacy status. Nothing to change here.
  • LIVE_DEBT_EXISTS: a non-terminal outbox debt still targets the credential. Wait for its settlement before recording a legacy clearance.
still_reported_as_orphanedboolean required

True when the account remains on the COGS orphan report — either the operator accepted the leak, or the row was not theirs to clear.

Changes

No recorded changes to this operation across all 1 revision of this API.