Getting Started
Quickstart
Send your first webhook event and watch it get delivered, signed, in about 10 minutes. Steps 1–5 happen in your dashboard; step 6 is the one line of code your service will actually run in production.
1
Create your account
Sign up at
accounts.lobthat.com/sign-up. This creates your organization automatically — no admin approval needed.Dashboard → Sign up
2
Create an Application
An Application is a container for one integration — its own event types, endpoints, and API keys. This gives you an
app_uid (e.g. app_01J0ZXYZ) you'll need in step 6.Dashboard → Applications → New Application
3
Create an Event Type
Register the event you're going to send, e.g.
order.created. This isn't optional — the ingestion API rejects any event type it doesn't recognize with event_type_not_found.Dashboard → Event Types → New Event Type
4
Generate an API key
This is the
whk_... key your server uses to publish events — shown once, so copy it now.Dashboard → API Keys → Generate
5
Add a subscriber endpoint
Grab a temporary inspectable URL from webhook.site, add it as an Endpoint, then subscribe it to
order.created (or the wildcard, to receive everything).Dashboard → Endpoints → New Endpoint → Subscribe
6
Publish your first event
This is the actual API call — everything above was one-time setup. Swap in your own
app_uid and API key.
curl
curl -X POST https://ingest.staging.lobthat.com/api/2026-06/app_01J0ZXYZ/events \ -H "Authorization: Bearer whk_<your_key>" \ -H "Content-Type: application/json" \ -d '{ "event_type": "order.created", "payload": { "order_id": "ord_123", "amount": 4999, "currency": "USD" } }'
A 202 response with
{"event_id": "..."} means the event was accepted and delivery was enqueued — it does not mean delivery succeeded. Check the next step to confirm it actually arrived.
7
Watch it arrive
Within a few seconds, the payload should land on your webhook.site page with three headers:
webhook-id, webhook-timestamp, and webhook-signature. You can also see the attempt (status code, latency, retries) in your dashboard's Delivery Logs.Dashboard → Applications → your app → Delivery Logs
Verifying the signature is a separate step your receiving server needs to do before trusting a payload — see Signature Verification for the full recipe and a reference implementation.