📡API Transaction Logs
API Transaction Logs give you an audit trail of 3rd‑party API traffic only. You see outbound requests from OnRaven to providers (e.g. Infobip, Meta, TikTok) and inbound notifications/webhooks from those providers (Zapier, Make, Infobip, Meta, TikTok, etc.). Internal calls to your own OnRaven API are not logged. Use this to debug integrations, verify webhooks, and audit provider traffic.
How to open API Transaction Logs
In the left sidebar, click API Transaction Logs (or find it under Settings, Integrations, or Analytics, depending on your app layout). You need the right permissions (e.g. Analytics or Integrations) to see this page.
What you'll see
The log is a table of requests (one row per request). Typical columns:
Date / Time
When the request happened.
Type
Inbound (request into OnRaven) or Outbound (request from OnRaven to an external service).
Provider
Source or destination (e.g. ZAPIER, MAKE, or blank for general API).
Method
HTTP method (POST, PUT, PATCH, DELETE). GET requests are not logged to keep the log focused on changes and webhooks.
Request path
The API path that was called (e.g. /v1/bots/zapier/...).
Status
HTTP status code (200, 400, 500, etc.).
Request IP
IP address of the caller (for inbound).
You can often expand a row or open a detail view to see request headers, request body, and response body (sensitive fields may be redacted). Use this to debug why a webhook failed or what payload was sent.
Filters
Use filters to narrow down the list:
Transaction ID — Search by the unique ID for that request.
Start / End time — Date range for when the request occurred.
Provider — e.g. Zapier, Make, or All.
Method — POST, PUT, PATCH, DELETE, or All.
Request path — Filter by path (e.g. only webhook URLs).
Response status — Filter by HTTP status (e.g. only errors: 4xx, 5xx).
Click Apply filters to update the table, and Reset to clear them.
What gets logged
Only 3rd‑party API traffic is logged:
Inbound: Webhooks and notifications from external providers into OnRaven (e.g. Zapier, Make, Infobip, Meta, TikTok). Each inbound request that is explicitly logged by the integration (e.g. when a webhook is received) appears here.
Outbound: Requests from OnRaven to external APIs (e.g. Infobip for SMS/RCS, Meta for WhatsApp/Instagram, TikTok) when the integration records them.
Not logged: Internal requests to your own OnRaven API (e.g. dashboard, workflow builder, settings). Only traffic to or from 3rd‑party providers is recorded.
Common uses
Debug a webhook
Filter by Provider (e.g. Zapier) and time range, find the request, open details to see request/response body and status.
Check for errors
Filter by Response status (e.g. 400, 500) to see failed calls.
Verify a specific call
Use Transaction ID if you have it from an error message or support.
Audit integration traffic
Filter by Provider and date range to see how often a integration is being called.
Who can see API Transaction Logs
Access is usually limited to Admins or roles with Analytics (or similar) permission. If you don’t see API Transaction Logs in the sidebar, your role may not have access. Ask your admin if you need it.
Troubleshooting
Don’t see API Transaction Logs
Your role may not have permission. Ask your admin.
Log is empty
Check the date range and filters. Try “Reset” and a wider time range. Only 3rd‑party traffic (outbound to Infobip/Meta/TikTok and inbound from Zapier/Make/Infobip/etc.) is logged.
Missing a request
Internal API calls are not logged. Only requests to or from external providers (Zapier, Make, Infobip, Meta, TikTok, etc.) appear.
Need request/response body
Open the row detail; bodies are shown there (with sensitive fields redacted).
For setting up webhooks and integrations, see Integrations and Lead Automations. For user actions (who did what in the app), see Activity Logs.
Last updated
Was this helpful?