curl --request POST \
--url https://api.messaging.phonovation.com/whatsapp/1/conversions \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"sourceId": "263258390011723",
"conversions": [
{
"ctwaClickId": "ARAkLkA8rmlFeiCktEJQ-QT",
"type": "PURCHASE",
"details": {
"currency": "USD",
"value": 100
},
"conversionTime": "2024-05-14T10:11:45.057+0000"
}
]
}
'Submit conversions
Submit WhatsApp conversion events. Events 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 \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"sourceId": "263258390011723",
"conversions": [
{
"ctwaClickId": "ARAkLkA8rmlFeiCktEJQ-QT",
"type": "PURCHASE",
"details": {
"currency": "USD",
"value": 100
},
"conversionTime": "2024-05-14T10:11:45.057+0000"
}
]
}
'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
Conversion events collection.
1 - 1000 elementsShow child attributes
Show child attributes
Conversion events source identifier. In case of ads that click to WhatsApp, it should be the Facebook Page selected through Ads manager and through Exchange app. Could be omitted if only one page is connected through Exchange app.
Response
Conversions were submitted