PayloadPigeon

Test HTTP and WebSocket traffic in Chrome. Modify API responses and WebSocket messages, reproduce edge cases, save reusable tests.

PayloadPigeon helps developers test frontend and backend behavior using the real HTTP and WebSocket traffic their applications already generate. Instead of rebuilding requests from scratch, start Capture for the tab you want to test, perform an action in your application, and work with the traffic that follows. Use PayloadPigeon to: • Capture real HTTP requests, responses, and WebSocket traffic from the selected tab. • Focus on traffic after a user action with automatic Actions and `After:` filtering. • Inspect URLs, headers, bodies, status codes, and supported WebSocket messages. • Modify a fresh HTTP response and see how the real frontend reacts. • Edit a captured HTTP request and send it to the backend again. • Modify, delay, or drop supported WebSocket messages and test the resulting application behavior. • Use View Activity to see related HTTP and WebSocket events from one action in a single timeline. • Save useful scenarios as reusable Tests. • Add Starting state and Expected behavior so the human context stays with each Test. • Organize Tests into Test Plans. • Repeat saved checks while fixing bugs or after changing your application. • Record successful checks or problems as Results and keep useful technical evidence with them. PayloadPigeon supports both frontend and backend testing workflows. For frontend checks, configure a supported HTTP response or incoming WebSocket behavior, choose Ready, and repeat the relevant action in your application. PayloadPigeon applies the configured behavior to fresh matching traffic so you can see how the application responds. For backend checks, start from a request your application already sent, modify it if needed, send it again, and inspect the real response. PayloadPigeon is designed for manual behavioral and regression testing. It does not automatically execute an entire Test Plan — you choose and run each Test yourself. Capture is explicit: you choose the tab and start it yourself. Chrome may display a debugging notice while Capture is active because PayloadPigeon uses Chrome’s debugger API for browser-level network access. Local-first by design: core testing runs in your browser. Saved Tests, Test Plans, and Results are stored locally in encrypted storage protected by your PayloadPigeon password. No PayloadPigeon account or cloud synchronization is required for your saved library. Captured traffic can contain sensitive information such as URLs, headers, bodies, authentication data, and WebSocket messages. Captured traffic is not uploaded to PayloadPigeon for storage or analytics. Backend Send contacts only the destination you choose. The public PayloadPigeon Playground uses the PayloadPigeon demo service. Optional anonymous feature-usage analytics is disabled until you choose to enable it in Data & privacy. Analytics contains aggregate feature-use counts and does not include captured traffic. No application code changes are required. All features are available free during PayloadPigeon Early Access. Learn more, watch the current tutorial, review data-handling details, and try the public Playground at payloadpigeon.com.