Trusted by 60,000+ developers worldwideKapso logs every request your app sends to WhatsApp. Search by status, endpoint, or API key to see why one failed.
Open any request to see what your app sent and what came back, without adding logging to your own code.
Hand a failed request to Kapso Agent, or view it in context to see the Meta events and webhooks around it.
See how long the call took and which key sent it, so you can tell production from a test script.
Endpoint, status, and API key are all searchable, like response_status:422.
The request body and the error that came back, with tokens and keys removed.
Search a phone number or message ID to see everything that happened to it: the API call, Meta's updates, your webhooks, and the workflows that ran.
| Time | Source | Summary | Status | What happened |
|---|---|---|---|---|
| Oct 7, 10:42:18 | API | POST /meta/whatsapp/v24.0/…/messages | HTTP 200 | Your app sends an order update |
| Oct 7, 10:42:19 | Meta | Message sent | Sent | Meta accepts it |
| Oct 7, 10:42:21 | Meta | Message delivered | Delivered | It reaches the customer's phone |
| Oct 7, 10:42:21 | Webhooks | whatsapp.message.delivered | HTTP 200 | Kapso tells your server |
| Oct 7, 10:43:05 | Messages | Where is my order? | Received | The customer replies |
| Oct 7, 10:43:06 | Workflows | step_completed / send_tracking | Completed | Your workflow answers |
| Oct 7, 10:43:06 | Functions | get-tracking · 240 ms | HTTP 200 | …using your function |
The same search runs in the dashboard, the Platform API, the Kapso CLI, and Kapso Agent.
List API logs with filters for endpoint, status, and errors, or search every source.
Search logs from your terminal or a coding agent, with the same filters.
Ask Kapso Agent from any failed event and it explains what went wrong, with the logs already loaded.
The method, endpoint, status, response time, API key, IP address, and request parameters with sensitive values removed. When a request fails, the error response is saved too.
Only for failed requests. When a request returns an error, Kapso saves the error it returned. Successful response bodies aren't stored.
The Free plan includes 100,000 log events a month. Paid plans include more, and extra events are billed per million. See pricing for your plan.
Yes. Use the Platform API, kapso logs search in the Kapso CLI, the search_logs tool in the Kapso MCP server, or hand a failed event to Kapso Agent.
2,000 free messages/month. $2 in credits included. No credit card required.