Network Requests
Capture full API request and response data including headers, bodies, and timing.
Overview
VibeCheck monitors all XHR and fetch requests made by the page during a recording. Every request is captured with its full request and response data, making it easy to identify API-related bugs.
What gets captured
For each network request, VibeCheck records:
| Field | Details |
|---|---|
| Method | GET, POST, PUT, DELETE, PATCH, etc. |
| URL | Full request URL including query parameters |
| Status | HTTP status code (200, 404, 500, etc.) |
| Request headers | All headers sent with the request |
| Request body | POST/PUT body content (JSON, form data) |
| Response headers | All headers returned by the server |
| Response body | Response content (JSON, text) |
| Timing | Request duration in milliseconds |
| Timestamp | When the request was made relative to recording start |
Viewing network data
On the VibeCheck platform, the Network tab shows all captured requests in a list. Each entry displays:
- Status code with color coding (green for 2xx, red for 4xx/5xx)
- HTTP method and URL
- Response time
Click on any request to expand and view the full request/response details.
Identifying issues
Network data helps developers quickly identify:
- Failed requests — 4xx and 5xx status codes
- Slow responses — requests taking longer than expected
- Missing data — expected API calls that never happened
- Wrong payloads — incorrect data being sent to the server
Exporting
Network data can be exported as JSON, which is useful for:
- Sharing with backend developers
- Replaying requests in tools like Postman or curl
- Adding to issue tracker tickets
Tips
- Sort by status to find failed requests quickly
- Check response bodies for error messages from the API
- Compare timing to identify slow endpoints
- Cross-reference with console — API errors often produce console errors too