NewThe global rate limit drops to 1000 requests per minute
BeeL
Get StartedMulti-NIFVeriFactuStripeAPI ReferenceChangelog

Read your API request logs

A new Request Logs endpoint family lets you inspect the requests your own API keys have made (live + test) — method, path, status, timing, and the full request/response detail — so you can correlate and debug integrations without leaving your stack.


Changelog

A new Request Logs endpoint family lets you inspect the requests your own API keys have made (live + test) — method, path, status, timing, and the full request/response detail — so you can correlate and debug integrations without leaving your stack.

What else changed

  • GET /v1/developers/request-logs — list your past API requests, cursor-paginated. Filter by environment (live/test), only_errors, method, http_status, path_contains, api_key_id, and a from/to time range. By default the last 30 days are returned.
  • GET /v1/developers/request-logs/{request_id} — full detail of a single request, including request/response bodies and headers. Pass the optional timestamp hint (the value from the list) to look up logs older than the default window.
  • Cursor pagination — navigate with the opaque next_cursor / prev_cursor returned in each response; has_next / has_previous tell you when you've reached the edges.
  • Correlate with X-Request-Id — each log's request_id matches the X-Request-Id response header (and meta.request_id), so you can jump straight from a live response to its full log.
  • Works with your existing API key (Authorization: Bearer) — no extra scope required.

Endpoints

  • GET/v1/developers/request-logsList your API request logs (cursor-paginated, filterable by environment, status, method, path, key and time range)
  • GET/v1/developers/request-logs/{request_id}Get the full detail (bodies + headers) of a single request log

Where to go next