Verifications

Free reuse of a verification that already received a code

Re-arms the same number to receive another SMS while the rental's window is still open. Free because the original rental still owns the number.

Callers should check allow_reuse on the verification resource before calling. The rental may have transitioned states between your last GET and this call - in that case the API returns 409 REUSE_NOT_ALLOWED. Per-rental cooldown is 30 seconds.

Reuse is not supported on every catalog service. When unavailable the API returns 409 NOT_SUPPORTED; check allow_reuse on the verification first to skip the round trip.

post/verifications/{id}/reuse

Request

Base URL: https://dashboard.voidmob.com/api/v1
URL: https://dashboard.voidmob.com/api/v1/verifications/{id}/reuse
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

Reuse successful; the verification resource is re-armed and ready for a new code.

successtrue required

Example response

{
  "data": {
    "verification": {
      "id": "ver_01HXYZ123ABC",
      "display_id": "SMS7K4P2N",
      "phone_number": "+15551234567",
      "service_id": "svc_telegram",
      "service_name": "Telegram",
      "code": "123456",
      "paid_reuse_price_cents": 50
    }
  }
}

Changes

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