What does a managed webhook service do?

It sits between your callers and your services and authenticates, validates, and delivers HTTP traffic: fanning out to many targets, streaming responses back, or screening inbound requests. You don’t build that infrastructure yourself.

What can EchoRelay do for my HTTP traffic?

Fan out one request to several asynchronous targets, return a synchronous response, forward an SSE or chunked stream, or screen inbound requests before delivering them to your service.

Where does EchoRelay run?

Production runs in EU Central, on infrastructure we operate.

Webhook relay service

A webhook relay service for both directions.

EchoRelay sits in the middle of your HTTP traffic — the target your callers hit and the source that calls your services. One authenticated layer that fans out, streams, and shields, so you don’t build the plumbing.

Worked example

Ask a partner to validate an address and return its answer

Your app uses camelCase fields, while your address-validation partner expects underscores. Configure a synchronous target so your caller receives the partner's answer in the same request. This example uses a fictional API.

Your app sends to EchoRelay

{
  "postalCode": "10115",
  "country": "DE"
}

Your partner receives

{
  "postal_code": "10115",
  "country_code": "DE"
}

Your partner answers; your caller receives

{
  "city": "Berlin",
  "valid": true
}

Add one synchronous target with your partner's URL and authentication.
Map postalCode to postal_code and country to country_code.
Publish and call your EchoRelay endpoint. Leave the answer mapping unset to pass the partner's response body through.

Synchronous delivery has no automatic retries. If you need to send an event to several services and retry failures, configure asynchronous targets instead.

Configure the partner's request mapping.

Why EchoRelay

Less to build, less to run.

Both directions

The target your callers hit and the source that calls your services: one service, three shapes.

Authenticated and validated

Every request is authenticated, validated against your rules, and rate-limited before it moves.

Asynchronous retries

Asynchronous deliveries use retries with backoff and a replayable dead-letter queue. Synchronous and streaming deliveries have no automatic retries.

Questions

Answered, honestly.

What does a managed webhook service do?: It sits between your callers and your services and authenticates, validates, and delivers HTTP traffic: fanning out to many targets, streaming responses back, or screening inbound requests. You don’t build that infrastructure yourself.
What can EchoRelay do for my HTTP traffic?: Fan out one request to several asynchronous targets, return a synchronous response, forward an SSE or chunked stream, or screen inbound requests before delivering them to your service.
Where does EchoRelay run?: Production runs in EU Central, on infrastructure we operate.

Connect everything. Deploy nothing.

Start free See all three shapes

No credit card required.