The Analytics section has two new reports: the API request log and the webhook log. You can now see what your integration sent to Kwiga and what Kwiga sent to you — and find out why something did not work without contacting support.
API request log
Every request to the public API, with its address, response status, duration, token and IP. Open a request to see its parameters, request body and response. Narrow the list by period, method, endpoint, status, error reason or token, find a specific request by Request-Id or idempotency key, and export the list to a file. A request can be copied as a curl command to replay it on your side.
Every API response now carries a Request-Id. Keep it in your integration's logs and quote it when contacting support — the request is found right away. The log keeps requests for the last 30 days. How requests, responses and the Request-Id work — see the API documentation.
Webhook log
Every webhook sent from automations and CTA forms, with all delivery attempts, the recipient's response and the error if the call failed. Show only failed calls, filter by source or recipient address, and export the list. The log opens in one click from the webhook settings in an automation. It keeps calls for the last 90 days. How to set up the webhook itself — see Sending a webhook to transfer data to another service.
Who can see the logs
The project owner sees both logs right away. Staff members get access in their role settings, in the Analytics section. Tokens and secrets in addresses and headers are hidden in the logs.