Quick Start
Dumperoo offers two ways to capture and inspect HTTP requests:
Basic Usage
Quick Capture
1. Send any HTTP request to:
2. View the captured request at:
Example using curl (API echo):
-H "Content-Type: application/json" \
-d '{"test": "data"}'
Persistent Sessions
1. Create a new session:
2. Use this endpoint for webhooks and callbacks:
3. Monitor live webhook activity in your session viewer
Perfect for payment callbacks, GitHub webhooks, and integration testing
What Gets Captured
Request Details
Metadata
Security & Privacy
⚠️ Important Security Notice
Dumperoo is a public service. Anyone with access to your session ID or path can view your captured requests.
DO NOT send sensitive data such as API keys, passwords, tokens, or personal information through Dumperoo.
Use Dumperoo only for development and debugging purposes with non-sensitive test data.
🔒 Session ID Best Practices
Use system-generated UUIDs when possible. The "Create Session" feature generates cryptographically random session IDs that are much harder to guess.
Avoid predictable paths. If you choose your own session ID or path, use random, unguessable values. Avoid simple names like "test", "webhook", or "api".
Enumeration attacks are possible. Malicious users may attempt to guess session IDs to view other users' data.
✅ Recommended Usage
Common Use Cases
🔗 Webhook Testing (Sessions)
Monitor webhooks from GitHub, Stripe, Shopify in real-time. Perfect for debugging callbacks.
https://dumperoo.com/stickydump/abc123/webhook
🐛 API Echo & Testing (Quick)
Use as API echo endpoint to test client apps. View request/response immediately in browser.
https://dumperoo.com/dump/api-test
📱 Client App Testing (Quick)
Test mobile/web apps by pointing requests to quick capture for instant debugging.
https://dumperoo.com/dump/mobile-test
🔍 Form Debugging (Quick)
Debug HTML form submissions by pointing action to quick capture endpoint.