Create Account Closure
POST/b2b/users/:user/account-closures
Request closure of an Embed user account.
Closure is asynchronous. After a successful create call, poll
Get Account Closure or retry with the same
idempotency_key to track progress.
End-user closures (requested_by=user, closure_reason=user_request):
the user must clear remaining crypto balances before closure completes. Embed
does not liquidate assets on their behalf.
Compliance closures (requested_by=partner with a compliance reason):
Embed may liquidate remaining assets into base_currency before closing the
account. When liquidation runs, the response includes a linked
liquidation.liquidation_id that you can inspect with
Get Liquidation.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 408
- 409
- 429
- 500
- 503
Closure request accepted
Bad Request — the request was malformed or contained invalid parameters. Not retryable.
Unauthorized — authentication failed or credentials are missing/invalid. Not retryable.
Forbidden — the authenticated user does not have permission to perform this action. Not retryable.
Not Found — the requested resource does not exist. Not retryable.
Request Timeout — the request took too long to process. Retryable.
Conflict — the request conflicts with the current state of the resource. Retryable in some cases (see error code).
Too Many Requests — rate limit exceeded. Retryable with backoff.
Internal Server Error — an unexpected error occurred. Generally retryable.
Service Unavailable — the service is temporarily unavailable. Retryable.