WhatsApp Calling

Start caller-ID verification for a customer-brought number

Customer-brought (BYO) WhatsApp numbers cannot present themselves as caller ID on tel: call forwards until verified (carrier anti-spoofing); until then forwarded calls show a Zernio number (callerIdMode: platform on the calling config). This sends a one-time code to the number by SMS or voice call. Re-POST to resend. Zernio-purchased numbers never need this and get a 400.

Billing: Request; paid actions are priced in credits (see GET /v1/messaging/prices) · Rate limit: 60/min

post/v1/messaging/phone-numbers/{id}/whatsapp/caller-id-verification

Request

  • Base URL: https://apihub.co.il
  • URL: https://apihub.co.il/v1/messaging/phone-numbers/{id}/whatsapp/caller-id-verification
  • Auth: HTTP bearer

Path parameters

idstring required

Phone number record ID (from GET /v1/phone-numbers).

Headers

Idempotency-Keystring

Replay-safe: the same execution is returned instead of charging twice

X-Tagstring

Group calls into one job (e.g. one video) — see GET /v1/usage?tag=…

Request body

method'sms' | 'call'

Response

Completed

idstring

Execution id — stable across internal retries; use it with GET /v1/executions/{id}

status'pending' | 'processing' | 'completed' | 'partial' | 'failed' | 'cancelled' | 'timeout'
operationstring
tagstring nullable

Your X-Tag, if sent

created_atstring date-time
completed_atstring date-time nullable
errorstring nullable

Changes

No recorded changes to this operation across all 2 revisions of this API.