Paid reuse of an expired or completed verification
Reclaims a number from the available pool by charging a fixed paid_reuse_price_cents (currently 50 = $0.50). The charge happens atomically; on any failure (number left the pool, eligibility closed) the wallet is refunded and the call returns 409 REUSE_NOT_ALLOWED.
You must send accept_charge_cents in the body matching the current paid_reuse_price_cents - this is an explicit consent guard against accidental charges. Read the value off the verification resource instead of hardcoding.
After a paid reuse allow_paid_reuse flips to false; it re-arms once the number reaches the next eligible state transition (the reused rental expires, is confirmed, or receives a message), at which point a further paid reuse becomes available again - best-effort.
Per-rental cooldown is 30 seconds. LTR rentals must re-rent through the create endpoint instead.
Request
- Base URL: https://dashboard.voidmob.com/api/v1
- URL: https://dashboard.voidmob.com/api/v1/verifications/{id}/reuse/paid
- Auth: HTTP bearer
Path parameters
Opaque verification (SMS rental) identifier.
Headers
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.
Request body
Example request
{
"accept_charge_cents": 50
}Response
Paid reuse successful. charged_reuse_cents reflects what was deducted.
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.