API reference · Dashboard

List request logs

This workspace's API traffic, newest first.

gethttps://api.integrable.cloud/api/logs

Authentication: Bearer token
Retries: Safe to repeat
Body: None
Version: 2026-09-03

Only requests authenticated with an API key appear here. The dashboard's own calls are not logged - they are not anybody's integration, and logging them would bury the rows that are.

Metadata only: no request or response bodies are recorded, ever. Retention follows the plan, from one day on Free to a year on Enterprise.

Query parameters

limitinteger
Default: 50·≥ 1 and ≤ 200
cursorstring | null
api_key_idstring | null
status_classstring | null
One of 2xx, 3xx, 4xx, 5xx, or errors for everything >= 400.
methodstring | null
path_containsstring | null
Substring of the templated path, e.g. bots or knowledge.
request_idstring | null
The X-Request-ID from a response. This is the lookup to use when a customer quotes an error - it resolves to the exact call.
since_hoursinteger | null
≥ 1 and ≤ 2160

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+json with error.code set to validation_error. Its details name each field that failed and why.

Example request

curl

curl "https://api.integrable.cloud/api/logs" \
  -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 Dashboard endpoints

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.