Response Configuration
By default, your bin responds with 200 OK to every request. You can customize the response to test how webhook senders handle different scenarios.
Accessing Response Config
- Open your bin in the inspector
- Click the Settings gear icon
- Find the Response Configuration section
Options
Status Code
Any valid HTTP status code (200–599):
| Code | Meaning | Use Case |
|---|---|---|
| 200 | OK | Default — acknowledge receipt |
| 201 | Created | Simulate resource creation |
| 204 | No Content | Acknowledge without body |
| 400 | Bad Request | Test sender error handling |
| 401 | Unauthorized | Test authentication retry |
| 404 | Not Found | Simulate endpoint removal |
| 429 | Too Many Requests | Test rate limit handling |
| 500 | Internal Server Error | Test retry behavior |
| 503 | Service Unavailable | Test circuit breaker patterns |
Response Headers
Add custom headers to the response. Enter as key-value pairs:
Content-Type: application/json
X-Request-Id: abc-123
Retry-After: 60
Response Body
Set a custom response body. The content type should match the Content-Type header you configure.
JSON example:
{
"status": "received",
"id": "evt_123"
}
Plain text example:
OK - Webhook received
Response Delay
Delay the response by 0–10 seconds. The server waits the specified time before sending the response.
Use cases:
- Test timeout behavior (most webhook senders have 5–30 second timeouts)
- Simulate slow processing
- Test retry logic when responses are delayed
Important Notes
- Response configuration applies to all requests to the bin — you can't set different responses for different requests
- Changes take effect immediately for new requests
- The delay is server-side — the connection stays open during the delay
- Response configuration is saved with the bin (persists across sessions for persistent bins)