Use the bearer token generated in the dashboard to authorize server-to-server calls.
Messaging API to integrate WhatsApp with your ERP, CRM or system.
WPP Marketing's Developer API allows ERPs, CRMs, custom stores or internal systems to send messages via WhatsApp and retrieve message histories and webhook delivery records using REST endpoints, bearer token authentication and Swagger documentation.
Use the messaging API when your system needs to send WhatsApp messages.
The API Developer is intended for ERP, CRM, custom store, backoffice, or proprietary systems that need to initiate messages. Commercial events and delivery status callbacks use, respectively, the Events API and status webhooks.
Send operational messages within WhatsApp's allowed rules and time windows.
View the history of sent messages and their statuses using the GET /messages endpoint.
Configure the return events and check delivery results using the GET /webhooks endpoint.
What this page covers.
This page presents the Developer API endpoints for sending messages and querying histories. The Events API and receiving status webhooks have their own pages.
Sends a text message to a WhatsApp number.
TextoSend an image, audio, video, or document using a public HTTPS URL.
MídiaCheck the history of sent messages with status and pagination.
HistóricoCheck webhook deliveries with event, HTTP result, attempts and pagination.
WebhooksInteractive documentation with contracts, examples, required fields, and expected responses.
DocsAPI Developer does not replace Events API or status webhooks.
Each feature has a different direction. This separation prevents brittle integrations and makes it clear who calls whom in each flow.
Your system calls WPP Marketing to send text or media messages and to query message histories and webhook deliveries.
Your system sends commercial events such as order created, payment approved, shipment, or abandoned cart.
WPP Marketing sends standardized creation, delivery, read, and error events to a URL you provide.
Use the interactive documentation to validate payloads, authentication, and responses before deploying to production.
Tokens must stay on the backend. Do not expose credentials in public pages, front-end apps, or repositories.
Log events, handle API errors, respect operational limits, and validate numbers before sensitive sends.
Ready to integrate your system with WPP Marketing?
Open the Swagger to view Messaging API endpoints, payload examples, bearer token authentication, and expected responses. For shop events and delivery feedback, also see Events API and Webhooks de status.