Inspect API and provider request logs

Request Logs is where you look up what actually happened on a past request — the API calls made to Nash and the requests Nash made to your delivery providers, with their bodies, status codes, and timing. It's a debugging tool: it shows what already happened, it doesn't make anything happen.

Find it under Settings ▸ Connections ▸ Request Logs. The page subtitle reads View API request logs and history.

Note

The Connections group is hidden for provider organizations, so request logs only appear for operator orgs.

Find a request

The toolbar filters the list on the left; select a row to read its detail on the right.

• Date range — set a start and end date and time. The picker covers roughly the last 28 days, and it opens on today.
• Search — enter a request id to look one up exactly. You can also search by a job_ id or an ord_ id to find the requests tied to that job or order.
• Method, Status Code, Path, and User ID — filter dropdowns. Each option shows how many requests match, and you can select several at once.

Note

The date range reaches back about 28 days. If an older request doesn't appear, it may be outside that window — reach out to Nash about exact retention.

Read a request

Select a row to open its detail. The Information card shows the request's ID and URL (each with a copy button), plus its Method, Timestamp, User Email, Request Action, Status Code, and Latency (shown in milliseconds). Below the card, side-by-side Request and Response viewers show the JSON bodies; a side with nothing shows No data.

Status codes are color-coded in the list and the detail: a 2xx response is green, a 4xx is amber, and anything else — including 5xx — is red.

Share a request

Each row has a copy-link button that copies a shareable link to that request. Opening the link brings the recipient to Request Logs pre-filtered to it.

Note

Request Logs is also deep-linked from an order's activity, so you can jump straight from an event to the request behind it — see order timeline and status.

Reading the calls themselves

Request Logs shows you what a call did. For what the endpoints are and how to make them — schemas, authentication, and error codes — see the developer docs at https://docs.usenash.com.

Related

• Generate and manage API keys — the keys behind the API requests you'll see logged here.
• Set up and manage webhooks — webhook delivery attempts and retries live in the webhooks dashboard, not here.
• Order timeline and status — the order activity view that deep-links into these logs.