List numbers for selection
Fetch the WhatsApp phone numbers available across the user's WhatsApp Business Accounts (WABAs) after a headless OAuth flow.
WhatsApp OAuth grants access at the WABA level. When a connected WABA has 2 or more phone numbers, you must call this endpoint to list them and then POST /v1/connect/whatsapp/select-phone-number to bind one to the Zernio profile. Single-phone WABAs auto-complete during the OAuth callback and never reach this endpoint.
Use the profileId and tempToken returned in the headless redirect (step=select_phone_number).
Alternative: if you already know wabaId and phoneNumberId (e.g. from Meta Business Suite), use connectWhatsAppCredentials instead, which skips this two-step flow.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Query Parameters
The Zernio profile ID from the headless redirect
The temporary access token from the headless redirect
Header Parameters
Alternative auth for API users' end customers (used when the bearer token is scoped to a different user)
Response Body
application/json
application/json
application/json
application/json
{ "phoneNumbers": [ { "id": "1875844705851813", "display_phone_number": "+55 83 8793-2039", "verified_name": "Bioface", "quality_rating": "GREEN", "name_status": "APPROVED", "messaging_limit_tier": "TIER_1K", "wabaId": "317766992490131", "wabaName": "Bioface WABA" } ]}Get Embedded Signup SDK config
The Meta app id and Embedded Signup configuration id the Zernio-hosted signup page uses to open Meta's popup. Integrators do not need this endpoint: start the hosted flow with `GET /v1/connect/whatsapp?signup=hosted` and send the user to the returned `authUrl`. Authenticates with an API key or with the connect token the hosted flow issues (`X-Connect-Token` header).
Complete number selection
Bind a specific WhatsApp phone number to the Zernio profile after the user picks one from `listWhatsAppPhoneNumbers`. Exchanges the short-lived OAuth token for a long-lived token, subscribes the WABA to webhooks, and creates the SocialAccount.