Order, cart, payment, shipping, cancellation or registration takes place in the source system.
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.
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.
Records purchase intent and enables initial follow-up automations.
CarrinhoTriggers cart recovery with a reminder and return link when available.
RecuperaçãoNotifies order created or awaiting payment for transactional messages.
PedidoConfirms payment and allows a confirmation message, instructions, and next steps.
PagamentoSends shipping updates, tracking, or logistics status to reduce manual tickets.
EnvioFeeds the contact database for welcomes, relationship management, tags and campaigns.
ClienteThe 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.
Send stable identifiers to avoid duplication when the same event is resent.
Handle success, validation, and error responses in your backend to monitor the integration.
Send events only from the server and keep the token out of the frontend and public repositories.
Want to connect a custom store or ERP?
Open the Events API documentation to validate payloads, authentication, and examples before sending production events.