List recent WhatsApp conversion events
Returns the most recent conversion events sent through
POST /v1/whatsapp/conversions for the given WhatsApp account.
Sourced from delivery logs (Axiom late dataset), so the visible
window is bounded by log retention (about 30 days). Useful for
rendering a "recent activity" panel on the conversions setup tab
without standing up a parallel persistence layer.
Per-event payload mirrors the structured log we write on every
successful send: eventName, conversationId, eventsReceived,
eventsFailed, traceId, durationMs, and the wall-clock
timestamp.
API key authentication - use your Zernio API key as a Bearer token
In: header
Query Parameters
WhatsApp social account ID
Max events to return (1-200, default 50).
501 <= value <= 200Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.whatsapp.listWhatsAppConversions({ query: { accountId: 'account_abc123', },});console.log(data);{
"events": [
{
"timestamp": "2019-08-24T14:15:22Z",
"eventName": "string",
"conversationId": "string",
"eventsReceived": 0,
"eventsFailed": 0,
"traceId": "string",
"durationMs": 0
}
]
}{
"error": "Unauthorized"
}Get CTWA conversions dataset GET
Returns the Meta Click-to-WhatsApp conversions dataset currently linked to the WhatsApp account, if one has been provisioned. Reads only from the stored `metadata.metaCapiDatasetId` — never hits Meta, never creates a dataset. Use this to detect whether `POST /v1/whatsapp/conversions` is configured for an account.
Send WhatsApp conversion event POST
Forward a WhatsApp Business Messaging conversion event (`LeadSubmitted`, `Purchase`, `AddToCart`, `InitiateCheckout`, `ViewContent`) to Meta's Conversions API with `action_source = business_messaging` and `messaging_channel = whatsapp`. The endpoint looks up the originating CTWA click ID (`ctwa_clid`) captured on the first inbound message of the conversation and replays it on every event so Meta can attribute the conversion back to the Click-to-WhatsApp ad that drove the chat. Configuration prerequisites on the WhatsApp account metadata: - `metaCapiDatasetId`: the Meta Pixel/Dataset ID linked to the WABA. - `connectedFacebookPageId`: the Facebook Page paired with the WhatsApp Business number. Identify the conversation by either `conversationId` (preferred) or `phoneE164` (digits only, no `+`). At least one is required. If the conversation has no captured `ctwa_clid`, the request returns 422 because there is nothing to attribute. Token and dataset coupling: the WhatsApp account's accessToken must have access to the configured `metaCapiDatasetId`. By default a WABA's system-user token is scoped to the WABA's own Business Manager and cannot post to a pixel owned by a different Business; Meta returns code 100 in that case. Either share the dataset with the WhatsApp app's Business in BM, or use a dataset already in the same Business as the WABA.