Test Endpoints

HookWatch provides test endpoints to help you debug webhook integrations, simulate various response scenarios, and test your retry logic.

No Authentication Required

All test endpoints are public and don't require authentication. They're designed for quick testing and debugging.

Echo

Returns the complete details of your request including method, headers, body, and query parameters. Perfect for debugging webhook payloads.

POST /v1/test/echo

Accepts any HTTP method (GET, POST, PUT, DELETE, PATCH)

Example

curl

Response

Json

Delay

Responds after a specified delay. Use this to test timeout handling and slow response scenarios.

GET /v1/test/delay

Accepts any HTTP method

ParameterTypeDescription
delaynumberDelay in milliseconds (max: 30000ms / 30 seconds)

Example

curl

Timeout Limit

Maximum delay is 30 seconds. Requests exceeding this will respond immediately with an error.

Status

Returns a specific HTTP status code. Use this to test how your application handles various response codes.

GET /v1/test/status

Accepts any HTTP method

ParameterTypeDescription
codenumberHTTP status code to return (100-599)

Example

curl

Fail

Always returns a 500 Internal Server Error. Use this to test error handling and retry logic.

GET /v1/test/fail

Accepts any HTTP method

Example

curl

Common Use Cases

Test Webhook Flow

Use the echo endpoint as your destination to see exactly what HookWatch forwards.

Terminal

Test Retry Logic

Point your endpoint to the status endpoint with an error code to test retry behavior.

Terminal

Tips

  • Use the echo endpoint to verify webhook signatures before your server processes them
  • Combine delay and status endpoints to simulate slow, failing servers
  • Test endpoints work great with the CLI for local development debugging
  • Use status codes 429 (Rate Limited) or 503 (Service Unavailable) to test backoff handling

Related