Request logs
Inspect individual Piloterr API calls and debug failures.
Every call is recorded under API Logs, with the endpoint, status code, duration, caller IP, and credits charged. This is where you go when a request behaved unexpectedly.
Debugging a failed call
Find the request
Filter by date range, API key, endpoint, status, or IP — or paste a request ID straight into the search box.
Open the detail view
Click the row to open a panel with the parameters that were sent and the response that was returned.
Match it to a status code
400 means a parameter is wrong, 401 points at the key or a rate limit, 402 means an empty balance, and 500 is on our side and worth retrying.
Make the screen yours
- Toggle columns to show what matters to you: credits, speed, IP, parameters, or the error message.
- Switch to the time series view to see the same filtered traffic as a chart.
- Save a set of filters as a view so you can come back to it in one click.
- Turn on auto-refresh when you are watching a live incident.
What is stored
By default each row keeps the parameters that were sent and a truncated response body. If your workspace turns on log privacy under Settings → Account, parameters stop being stored — status, duration, and credit cost remain, so billing still works.
If your client reports a timeout but the log shows a 200, the call succeeded and your own runtime closed the connection early. Raise your HTTP timeout to 60 seconds.