Verifications

Mark a verification as done

Marks a verification as complete and moves it out of the active dashboard list into history. Local-only status flip - no refund, no external call, no balance movement. Use this when your integration has consumed the code and you no longer want the verification taking up space in the active view.

Valid while the verification is in waiting_for_code or code_received state, or when it has expired without a code. Once explicitly completed (or cancelled), the call returns 409 COMPLETE_NOT_ALLOWED.

Completion is optional - verifications automatically leave the active list when their rental window expires (~15 min). This endpoint just lets bulk callers tidy up sooner.

post/verifications/{id}/complete

Request

  • Base URL: https://dashboard.voidmob.com/api/v1
  • URL: https://dashboard.voidmob.com/api/v1/verifications/{id}/complete
  • Auth: HTTP bearer

Path parameters

idstring required

Opaque verification (SMS rental) identifier.

Example:ver_01HXYZ123ABC

Headers

Idempotency-Keystring required
Example:7c4f08c2-2a4f-4c8e-a1d2-9c2b9c8f7e10

Client-supplied key (any string, up to 255 chars) that scopes idempotent replay for write requests. Required on every POST, PATCH, and DELETE. Replays with the same key + same body return the cached response; same key with a different body returns IDEMPOTENCY_CONFLICT. Headers are case-insensitive; both Idempotency-Key and idempotency-key work.

Response

Verification marked complete.

successtrue required

Example response

{
  "data": {
    "verification": {
      "id": "ver_01HXYZ123ABC"
    }
  }
}

Changes

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