curl --request POST \
--url https://api.messaging.phonovation.com/whatsapp/1/conversions/waba \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"conversions": [
{
"conversionTime": "2024-05-14T10:11:45.057Z",
"ctwaClickId": "ARAkLkA8rmlFeiCktEJQ-QT",
"details": {
"currency": "USD",
"value": 100
},
"type": "PURCHASE"
}
],
"sourceId": "1234567890"
}
'Submit WABA conversions
Submit WhatsApp conversion events using your WhatsApp Business Account (WABA) phone number as the source. Each conversion event is linked to an ad click via ctwaClickId — a unique identifier contained within the inbound WhatsApp message originating from the ad. You can optionally include conversion details such as value and currency, and a conversion timestamp (up to 7 days in the past). Events are submitted in batches of up to 1,000 and are indivisible — either all are submitted or none.
Required scope: Enable one of: whatsapp:conversions.
curl --request POST \
--url https://api.messaging.phonovation.com/whatsapp/1/conversions/waba \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"conversions": [
{
"conversionTime": "2024-05-14T10:11:45.057Z",
"ctwaClickId": "ARAkLkA8rmlFeiCktEJQ-QT",
"details": {
"currency": "USD",
"value": 100
},
"type": "PURCHASE"
}
],
"sourceId": "1234567890"
}
'Authorizations
This is the most secure authorization type and the one with the most flexibility.
API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.
You can manage your API keys from GUI, or programmatically with dedicated API.
API key Authorization header example:
Authorization: App 003026bbc133714df1834b8638bb496e-8f4b3d9a-e931-478d-a994-28a725159ab9
Body
Sender as source identifier. This is the phone number registered via the embedded signup flow available in Exchange app.
"1234567890"
Conversion events collection.
1 - 1000 elementsShow child attributes
Show child attributes
Response
Conversions were submitted