Reading your API request logs
Updated June 29, 2026
When an integration or API call isn't behaving, the request log is the first place to look. It shows what was actually sent to Passmint and what came back, so you can tell a bad request from an unexpected response.
Where to find it
Open Developers → Logs. The log shows your most recent API requests for the mode you're viewing, so check test and live separately. Each entry lists:
- the method and path (such as
POST /v1/passes), - the status code,
- how long the request took, and
- when it happened.
Reading an entry
Expand an entry to see the full picture: the request body you sent, the response body Passmint returned, and any error message. This is usually enough to spot the problem on your own:
- A 4xx status means the request was rejected. The response body explains why, for example a missing required field or an unknown template.
- A 5xx status means something went wrong on the server side. If these persist, capture the timestamp and reach out to support.
- A request you expected but don't see in the log means it never reached Passmint. Check the key, the URL, and that your integration is actually firing.
Mind the mode. A request made with a pmk_test_ key shows up in the test log, and a
pmk_live_ key in the live log. If a call is missing, confirm you're looking at the
log for the same mode as the key you used.
Logs are a recent window
The log keeps your most recent requests, not your entire history. It's built for debugging what just happened, not long-term auditing. If you need a durable record of events, subscribe to webhooks and store them in your own system.