Connect WhatsApp
Verification status
Reads the number’s code_verification_status from Meta for one Cloud API channel.
- Bearer API key
- Scope:
reador write - or app session
- Workspace:
X-Tenant-ID(optional with a key)
Path parameters
iduuidrequiredChannel id (from
channels[].id).
Headers
AuthorizationstringrequiredYour API key as
Bearer <key>. The wordBearerand the space are case-sensitive. Browser clients signed in to the app use the session cookie instead.X-Tenant-IDuuidoptionalWorkspace id. Optional with an API key (a key always acts in its own workspace); if you send it, it must match the key’s workspace. Required with a session cookie. You can pass
?tenant=<id>instead.
Response
200 OKapplication/json
channel_iduuidChannel id.
phone_idstringMeta phone number id.
waba_idstringWhatsApp Business Account id.
phonestringSaved phone number.
statusenumMeta’s
code_verification_status:VERIFIED,EXPIRED,NOT_VERIFIEDorUNKNOWN.verifiedbooleantruewhen the number is verified.display_phone_numberstringmay be absentPhone number as Meta displays it.
Status codes
- 200OK. The verification status.
- 401Unauthorized. The API key is unknown, revoked or expired (
invalid or expired API key), or there is no key and no signed-in session (unauthorized). - 402Payment required. Only when subscriptions are enforced and the workspace has no active subscription. The body includes
code: "payment_required". - 403Forbidden. The
X-Tenant-IDheader ortenantquery does not match the API key’s workspace (API key belongs to a different workspace), or a signed-in user is not a member of the workspace (forbidden). - 400Bad request. Invalid input, or Meta rejected the request with a 4xx error.
- 404Not found. No Cloud API channel with this id in the workspace.
- 502Bad gateway. Meta returned a server error. Errors coming from Meta add
meta_code,meta_subcodeandmeta_titlewhen Meta provides them.