API ReferenceCurrent account activations

Resend the OTP for an in-flight activation

Path Parameters

activationId*string

Formatuuid

Response Body

`application/json`

`application/json`

`application/json`

`application/json`

`application/json`

curl -X POST "https://example.com/v1/user/accounts/current/activations/497f6eca-6276-4993-bfeb-53cbbbba6f08/resend"

Empty

{  "code": "BAD_REQUEST",  "description": "Bad Request"}

{  "code": "UNAUTHORISED",  "description": "Unauthorised"}

{  "code": "WAITING_LIST",  "description": "User is in the waiting list"}

{  "code": "TOO_MANY_REQUESTS",  "description": "Too Many Requests"}

{  "code": "INTERNAL_SERVER_ERROR",  "description": "Internal Server Error"}

Confirm the OTP for an in-flight activation POST

Verifies the code and moves the activation to OTP_CONFIRMED. The underlying account becomes ACTIVE once account opening is confirmed.

Start a current-account activation POST

Verifies KYC, submits (or reuses) the wallet onboarding, creates an activation row, and dispatches an OTP via SMS. If an activation is already in progress, that in-flight activation is returned instead, so a client that retries (e.g. after losing the activation id) resumes it rather than failing, and no duplicate OTP is sent. Returns 422 if KYC is not APPROVED, 409 if the onboarding has permanently failed and awaits an operator reset. A prior OTP-timeout rejection is self-recoverable and does not block a new attempt.