Request log

What this token has been doing. Useful when a call failed hours ago and nobody kept the response.

The object#

FieldTypeDescription
requestidstring(36)The X-Request-Id we returned. Quote it when you report a problem.
methodstring(10)
routestring(255)The matched route PATTERN, never the URI you sent. Ids and query values are deliberately not recorded.
httpstatusinteger
errorcodestring(40)Empty when the request succeeded.
durationmsintegerServer time, not round trip.
bytesininteger
bytesoutinteger
entrydatestring

Endpoints#

GET/requestlog 200

Read this token's own request log.

Every request this token made, newest first, so "it returned a 422 and I did not keep the body" is answerable without asking us. Two limits worth knowing before you rely on it. Logging is off unless it is switched on for the token, and only the last 100 requests are kept - it is a recent-history window for debugging, not an audit trail. If you need one of those, record the X-Request-Id on your own side as you go. A token only ever sees its own requests. There is no way to read another token's, including one belonging to the same user in the same company.

Requires scope setup:read.

Parameters
NameInTypeNotes
httpstatusqueryintegerOnly this HTTP status, e.g. 422. Named to match the field it filters.
failedquerystringPass true for everything that was not a 2xx.
routequerystringSubstring match on the route pattern, e.g. invoices.
methodquerystringOne HTTP verb.
pagequeryinteger1-based.
perpagequeryintegerDefault 50, maximum 200 - though only the last 100 requests are kept, so a larger page cannot return more.
curl \
  'https://acme.nolapro.com/!/api/v2/requestlog' \
  -H 'Authorization: Bearer $NP_TOKEN'