Environments

Keep provider callbacks straight across environments.

Local, staging, and production all want the same provider to call them, and the usual workaround is a tunnel someone has to remember to restart. Endpoints give each environment a permanent URL that keeps working whether or not anyone is at their desk.

Start free See pricing
A permanent URL per environmentFan-out to the service that should handle itAccess controls per endpoint
Workflow

How the debugging loop goes.

Create an endpoint per environmentName them for what they are (acme-local, acme-staging, acme-prod) and register each URL with the provider that should call it.
Register once, forget about itThe URL does not rotate, so provider configuration stops being something you redo every time a tunnel restarts.
Route traffic onwardAdd destinations so an endpoint relays what it receives to the service for that environment, while still keeping its own copy.
Lock down what mattersRequire a shared secret, or restrict an endpoint to a provider's IP ranges, when it is receiving traffic you would rather not have anyone else reach.
Details

Worth knowing before you wire it up.

Filter history by endpointWebhook history filters by endpoint and method, so "what did staging receive this morning" is a two-click question.
Network allowlistAn endpoint can be restricted to a list of IPs or CIDR ranges, which is the practical control when a provider publishes its egress addresses.
Shared secretEndpoints can require a SignalBin secret in a header or query parameter before accepting a request at all.
Learn more in the docs: Endpoints and destinations
FAQ

Common questions.

Is this a replacement for a local tunnel?

For receiving provider callbacks, yes: the URL is hosted and always up. If you need the request to reach a process on your laptop, pair an endpoint with the CLI destination kind rather than exposing your machine directly.

How many endpoints can I create?

Create as many as your environments need. Billing is based on the traffic received, not on how many endpoints exist.

Can teammates see the same endpoints?

Yes. Endpoints and webhook history belong to the workspace, and everyone you invite sees them.

Start with one endpoint.

Send a request, open the payload, and see exactly what your provider delivered.

Start free