Re-send a checkpoint code, or switch its method

Without challenge: re-sends the pending code or notification for account_id (a two_factor_app challenge has nothing to resend: resent:false). With challenge (an id from challenge_selection): switches to that method and returns the next 202 checkpoint.

post/v1/auth/checkpoint/request

Request

Base URL: https://api.curviate.com
URL: https://api.curviate.com/v1/auth/checkpoint/request
Auth: HTTP bearer

Request body

account_idstring required

The account whose pending checkpoint notification should be re-sent (returned with the 202 checkpoint_required response, or from link/poll).

challenge'email' | 'sms' | 'whatsapp'

Optional. An id from a challenge_selection checkpoint's challenges list: switches to that method and returns the next checkpoint. Omit to re-send the current code.

Response

The resend request was processed. resent:true means the substrate confirmed the notification was re-sent; resent:false means the substrate acknowledged the request but had nothing to re-send (e.g. a two_factor_app challenge, where the code is generated on the device), the response never claims a resend that did not happen.

object'checkpoint'

Response type discriminator.

account_idstring

resentboolean

Example response

{
  "safety_warning": {
    "row": "profile_views",
    "reset_at": "2026-09-05T00:00:00.000Z",
    "hint": {
      "parameter": "profile_views.ceiling",
      "message": "This account is at its ceiling for profile_views. This action went through because profile_views.posture is warn, and it counted: 101 of 100 this window. Raise profile_views.ceiling, or wait for the window to reset at 2026-09-05T00:00:00.000Z."
    },
    "reason": "ceiling",
    "blocked": false
  }
}

Changes

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