Phone Numbers

Request the WhatsApp verification code for a number

Starts (or restarts) WhatsApp verification of a Zernio-hosted number: adds it to Meta's pre-verified pool when needed and asks Meta to send the verification code, which Zernio captures on the number itself. Used to connect WhatsApp on a number bought for calls or SMS. /v1/whatsapp/phone-numbers/{id}/request-code is a deprecated alias with the same contract.

When Meta refuses the number for WhatsApp (Meta error 136021): a number that is already live (active or suspended) is left untouched and keeps working for calls and SMS, and the call answers 409 number_not_whatsapp_eligible; buy a new number with WhatsApp enabled instead. A number that was never live (still verifying) is replaced at no extra cost with a WhatsApp-eligible number on the same record, answered as 200 with replaced: true.

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

post/v1/messaging/phone-numbers/{id}/whatsapp/request-code

Request

  • Base URL: https://apihub.co.il
  • URL: https://apihub.co.il/v1/messaging/phone-numbers/{id}/whatsapp/request-code
  • 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' | 'VOICE'

Delivery method for the code. Omit to let Zernio pick (SMS when the number can receive it, else VOICE).

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.