Get started
Send your first webhook in five minutes. See the Quickstart.
N 40° 42′ 46″ · W 74° 00′ 21″ REV 2024.11 · EDITION IV
Harbor
Webhook delivery as infrastructure — signed, retried, idempotent, observable.
- Uptime
- 99.998 %
- Signed
- HMAC-SHA256
- Retry budget
- 72 hours
- Edge
- 14 regions
What Harbor does
Section titled “What Harbor does”You POST events to Harbor. We deliver them to your customers’ HTTPS endpoints with retries, HMAC signing, idempotency, replay, and a dead-letter queue. You don’t run the retry scheduler. You don’t rotate signing keys by hand. You don’t lose deliveries when a customer’s endpoint has a bad five minutes.
Three nouns explain the whole system: destinations (where events go), events (what you send), and deliveries (each attempt, with status and response). Everything else is a detail about one of those three.
01DestinationsHTTPS endpoints with their own signing secret, retry policy, and active/paused state.
02EventsTyped payloads you POST to Harbor. Subscriptions fan them out to destinations.
03DeliveriesEach attempt — status, response code, latency, retry lineage. The audit trail.
Chart the course
Section titled “Chart the course”Core concepts
Destinations, events, and deliveries — the three nouns that explain everything.
API reference
Every endpoint with parameters, returns, and curl examples.
Start with Destinations.
Troubleshooting
HMAC signature mismatches, retry storms, duplicate deliveries — the classics, with how to fix them. See Troubleshooting.
Harbor · est. 2024 · built for engineers who’d rather not run their own retry scheduler