Connect WhatsApp from Embedded Signup
Changed onExchange the authorization code Meta's Embedded Signup popup returned. This is the call the Zernio-hosted signup page makes after the popup closes (GET /v1/connect/whatsapp?signup=hosted), sending the wabaId and phoneNumberId Meta reported so exactly the chosen number is connected; when both are omitted the first number the token can see is used. The code never passes through a redirect_uri, so POST /v1/connect/{platform} cannot accept it. Authenticates with an API key, or with the connect token the hosted flow issues (X-Connect-Token header).
Request
- Base URL: https://zernio.com/api
- URL: https://zernio.com/api/v1/connect/whatsapp/embedded-signup
- Auth: HTTP bearer
Headers
Connect token issued by the hosted signup flow, accepted instead of an API key.
Request body
Response
Number connected
Changes
- warning
added the new
accountenum value to the/response property for the response status - warning
added the new
accountenum value to the/response property for the response status
- warning
- info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status
- info