API reference · Insights
Audit log
Who did what in this workspace.
- Authentication
- Bearer token
- Retries
- Safe to repeat
- Body
- None
- Version
- 2026-09-03
audit_logs has been written by identity, tenancy and the admin surface since the beginning, indexed on (org_id, created_at), and read by no endpoint in the product. This is that read.
Admin-level, not member-level: the log names people and includes IP addresses, and every operator impersonation of this workspace appears in it - which is the whole point, and also why it is not a viewer surface.
Query parameters
daysintegerDefault: 30·≥ 1 and ≤ 365
actionstring | nullUp to 60 characters
limitintegerDefault: 50·≥ 1 and ≤ 200
offsetintegerDefault: 0·≥ 0
Responses
- 200OKapplication/json
object
5 response headers
- RateLimit-Limit
Requests permitted in the current window.
- RateLimit-Remaining
Requests left in the current window. Back off before it reaches 0.
- RateLimit-Reset
Seconds until the current window resets.
- X-API-Version
The dated version of the API contract that served this response, e.g.
2026-09-03. Pin against it; it changes only when a response shape changes incompatibly.- X-Request-ID
Quote this in a support request to identify the call.
- 422Validation error
The shared error envelope, served as
application/problem+jsonwitherror.codeset to validation_error. Its details name each field that failed and why.
Example request
curl "https://api.integrable.cloud/api/audit-log" \
-H "Authorization: Bearer $INTEGRABLE_API_KEY"Set INTEGRABLE_API_KEY first. The same call from the TypeScript or Python SDK takes the same fields.
Errors
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-bot limit on top.
More Insights endpoints
- get/api/activityWorkspace activity
- patch/api/advice/{recommendation_id}Acknowledge a recommendation
- post/api/archive/importImport archive
- post/api/archive/viewView archive
- get/api/archivesList archives
- get/api/bots/{bot_id}/adviceBot recommendations
- get/api/bots/{bot_id}/archiveExport archive
- get/api/bots/{bot_id}/dashboardBot dashboard
- get/api/bots/{bot_id}/intentsVisitor intents
- get/api/bots/{bot_id}/reportBot report
- get/api/bots/{bot_id}/satisfactionSatisfaction
- get/api/bots/{bot_id}/trafficWebsite traffic
- get/api/creditsCredit balance
- get/api/credits/exportExport the credit statement
- get/api/credits/statementCredit statement
- get/api/dashboardOrg dashboard
- get/api/exportsList exports
- get/api/exports/formatsExport formats
- get/api/preferencesGet dashboard preferences
- put/api/preferencesSet dashboard preferences
- get/api/reportOrg report
Something here wrong or missing? Tell us — the documentation and the API are maintained by the same person, so a correction is a fix rather than a ticket.