What Gets Captured
Every log entry is a full snapshot of the HTTP exchange. You don’t need to configure anything to start capturing; logging is automatic and always on for every endpoint. Each log entry includes:string
The HTTP method of the incoming request:
GET, POST, PUT, PATCH, or DELETE.integer
The HTTP status code returned to the caller. For JSON endpoints this is always
200. For Forward endpoints it reflects your backend’s actual response.string
The full request path, including the slug and any path segments appended by the caller.
integer
Total round-trip time in milliseconds from when GetRequest received the request to when it returned a response.
object
All HTTP request headers sent by the caller, captured exactly as received.
string
The raw request body. Captured for
POST, PUT, and PATCH requests. JSON bodies are rendered in a readable format in the dashboard.object
Any query string parameters included in the request URL, parsed into key-value pairs.
object
Granular timing breakdown including time-to-first-byte and upstream response time (for Forward endpoints).
Filtering Logs
When you’re tracking down a specific failure, you can narrow the log view using two filters:Filter by Status Code
Filter to exact codes (
404, 500) or classes (5xx, 4xx) to isolate errors. Combine with a time range to find when a problem started.Filter by Time Range
Scope the log view to a specific window — last hour, last 24 hours, or a custom date range — to focus on the period you care about.
Log Retention
Log history is retained based on your plan:
Logs older than your plan’s retention window are automatically removed. If you need to preserve a specific request before it ages out, use the Share feature (Pro) to generate a shareable link. Share links remain accessible for 30 days from creation, independent of your log retention window.
Replay (Pro)
On the Pro plan, every log entry has a Replay button. Replay re-fires the original request — using the same method, headers, body, and query parameters — against your endpoint as it is configured right now.1
Open a log entry
Click any request in the Logs view to expand its full details.
2
Click Replay
Hit the Replay button to re-send the original request to your endpoint.
3
Review the result
GetRequest creates a new log entry for the replayed request. The original log entry is preserved untouched alongside it.
Replay always generates a new log entry. Your original request log is never modified or overwritten, so you maintain a clean audit trail of both the initial failure and the replayed result.
Share (Pro)
On the Pro plan, you can generate a public, read-only link to any log entry. Anyone with the link can view the full request and response details without logging in to GetRequest.No login required
Share links are accessible to anyone, making it easy to send a specific request to a teammate, a vendor, or a support ticket.
Expires after 30 days
Share links are valid for 30 days from the time they are created. After that, the link stops working.