What does Kapso log for each request?
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.
See every WhatsApp API call
Kapso logs every request your app sends to WhatsApp. Search by status, endpoint, or API key to see why one failed.
What a log tells you
- Ask Kapso Agent why a request failed, or view it in context with the Meta events and webhooks around it.
- How long each call took and which API key sent it, the request body, and the error that came back, with tokens and keys removed.
- Endpoint, status, and API key are all searchable, like response_status:422.
Follow a message from start to finish
- 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.
Search from code, the CLI, or an agent
- Platform API: GET /platform/v1/api_logs with filters for endpoint, status, and errors.
- Kapso CLI: kapso logs search --source external_api_log --problems-only --period 24h
- Kapso Agent: ask it about any failed event, with the logs already loaded.
Frequently asked questions
Are response bodies saved?
Only for failed requests. When a request returns an error, Kapso saves the error it returned. Successful response bodies aren't stored.
How many log events are included?
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.
Can I search logs from code or an agent?
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.