Request logs

FurniOps keeps a log of every API request your organisation makes: who called what, and what it answered. Use it to debug an integration from the server's side, to find the request behind a request_id a user reported, or to see what a key has been doing.

Read it in the dashboard under Developers › Logs, or with GET /v1/request-logs. It needs request_logs:read, which owners, admins and developers hold, and which an API key can hold.

What is loggedCopy Anchor Link

Every request one of your credentials made that reached a route, including the ones FurniOps refused (a missing permission, a rate limit, a bad FurniOps-Mode header):

{
  "object": "request_log",
  "id": "req_034aa2WBnMgynuvLmz3Pq8",
  "method": "POST",
  "path": "/v1/sources/src_034XqBaL2mRLTZPXyRbaUc/runs",
  "route": "/v1/sources/{id}/runs",
  "query": null,
  "status": 429,
  "error_code": "quota_exceeded",
  "duration_ms": 12,
  "actor": { "kind": "api_key", "id": "key_034XqBaL2mRLTZPXyRbaUb" },
  "livemode": true,
  "api_version": "2026-10-04",
  "idempotency_key": "nightly-run-2026-10-06",
  "ip": "203.0.113.0/24",
  "user_agent": "node",
  "created_at": "2026-10-06T09:12:44Z"
}

Bodies and credentials are never logged: neither what you sent nor what FurniOps answered.

Not logged:

• a 401: a request with no usable credential belongs to no organisation;
• reading the request logs themselves, so looking never adds to them;
• HEAD and OPTIONS requests.

A request appears within seconds. The log is a debugging aid, not a ledger: under extreme load a few entries may be dropped rather than slow your requests. For a record of changes, use the audit log.

How longCopy Anchor Link

Requests are kept 31 days, then deleted.

Each mode apartCopy Anchor Link

Logs belong to a mode. A test key reads the sandbox's requests, a live key the live ones; the dashboard's Logs show the mode the dashboard is in.

FilterCopy Anchor Link

The list is newest first and pages with limit (up to 100), starting_after and ending_before, like every list. In the dashboard the filters live in the URL, so a filtered view can be shared, and a request opens in a side sheet with its request, answer and caller.

With the SDK:

// Every refused request of the last hour, newest first, in the key's mode.
const since = new Date(Date.now() - 60 * 60 * 1000).toISOString();
for await (const log of furniops.requestLogs.list({ status: "4xx", since })) {
  console.log(log.created_at, log.method, log.path, log.status, log.error_code, log.actor.id);
}

Find one requestCopy Anchor Link

Every answer carries a Request-Id header, and every error a request_id. Log it in your client, then look it up:

// One request, by the `Request-Id` your client logged (or an error's `request_id`).
const log = await furniops.requestLogs.get("req_034aa2WBnMgynuvLmz3Pq8");
console.log(log.route, log.status, `${log.duration_ms} ms`, log.idempotency_key);

GET /v1/request-logs/{id} returns the newest request with that ID. Quote the same ID to FurniOps support.