Order, cart, payment, shipping, cancellation or registration takes place in the source system.
Events API
Send events from your store or ERP to trigger automations on WhatsApp.
Use the Events API when your own system needs to report cart, order, payment, shipping, cancellation, or customer creation to WPP Marketing.
The Events API receives the commercial event and uses the configured automations. To send a message directly, use the Messaging API. To track delivery, read receipts and errors, use the status webhooks.
Flow
Your system reports the event. WPP Marketing decides the automation.
The Events API is ideal for custom stores, ERPs, back offices, and integrations that don't have a plug-and-play connector.
Your backend sends the event with token, identifier, customer, values and available links.
WPP Marketing checks whether there is an active automation for that event and customer.
The customer receives WhatsApp messages for recovery, payment, order, shipping, campaign, or post-sale.
Supported commercial events.
Final naming and required fields must follow the Events API documentation.
POST
cart.created
Records purchase intent and enables initial follow-up automations.
Carrinho
POST
cart.abandoned
Triggers cart recovery with a reminder and return link when available.
Recuperação
POST
order.created
Notifies order created or awaiting payment for transactional messages.
Pedido
POST
order.paid
Confirms payment and allows a confirmation message, instructions, and next steps.
Pagamento
POST
order.shipped
Sends shipping updates, tracking, or logistics status to reduce manual tickets.
Envio
POST
order.cancelled
Logs the order cancellation to trigger the communication configured for this event.
Cancelamento
POST
customer.created
Feeds the contact database for welcomes, relationship management, tags and campaigns.
Cliente
Recommended data
The better the event, the better the automation.
The Events API must receive enough data to identify the customer, purchase, amount, status, and useful links for the message.
Phone number, name, email, country and external identifier help with deduplication and segmentation.
Number, external ID, total, currency, status, payment method and items make the message more useful.
Checkout, payment, tracking or order page may be used in automated messages.
Provide external_id or order.id and keep the source stable. Deduplication considers account, normalized source, event type, and external identifier. Repeated events return HTTP 200 with the indication Duplicate event ignored. This endpoint does not use the Messaging API Idempotency-Key header.
HTTP 200 confirms the event was processed, not that a message was delivered. Sending requires an active automation for the event, valid customer data, and a configured connection. Track the message via reports and status webhooks.
Create a credential with events:write and send events from the server. Keep the token out of the frontend and public repositories. Use customer.phone for the phone number and the customer and order objects as shown in the example and the OpenAPI contract.
Want to connect a custom store or ERP?
Open the Events API documentation to validate payloads, authentication, and examples before sending production events.