Order, cart, payment, shipment, cancellation, or registration happens in the source system.
Events API
Send store or ERP events to trigger automations on WhatsApp.
Use the Events API when your system needs to inform cart, order, payment, shipment, cancellation, or customer creation to WPP Marketing.
Flow
Your system reports the event. WPP Marketing decides the automation.
The Events API is ideal for custom stores, ERPs, backoffices, and integrations that do not have plug and play connectors.
Your backend sends the event with token, identifier, customer, values, and available links.
WPP Marketing checks if there is active automation for that event and customer.
Customer receives WhatsApp recovery, payment, order, shipment, campaign, or post-sale message.
Supported commercial events.
Final nomenclature and mandatory fields must follow the Events API documentation.
POST
cart.created
Registers purchase intention and enables initial follow-up automations.
Carrinho
POST
cart.abandoned
Triggers cart recovery with reminder and return link when available.
Recuperação
POST
order.created
Informs order created or awaiting payment for transactional messages.
Pedido
POST
order.paid
Confirms payment and allows confirmation message, instructions, and next steps.
Pagamento
POST
order.shipped
Sends shipping update, tracking or logistics status to reduce manual tickets.
Envio
POST
customer.created
Feeds contact database for welcome, relationship, tags, and campaigns.
Cliente
Recommended data
The better the event, the better the automation.
The Events API should receive enough data to identify customer, purchase, value, status, and useful links for the message.
Phone, 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 can be used in automatic 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 via 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.