Glossary

Webhook delivery

One attempt to POST an event to your endpoint. OneLifeVibe delivers at least once, so dedupe on the webhook-id header and answer 2xx fast.

Updated November 14, 2026

Also called
delivery

At OneLifeVibe

What it means

A webhook delivery is one attempt to POST an event to your endpoint. It is not the event itself, and it is not the subscription that decides which events you receive. It is the single HTTP request and whatever your server answers back.

OneLifeVibe treats delivery as at-least-once. The same event can reach you more than once. The webhook-id header carries the event id and stays the same on every attempt for that event, which makes it the value you dedupe on.

How it works

When an event fires, the platform sends a POST with a body describing the event and headers describing the request. Your endpoint answers with a status code, and that status decides what happens next. A 2xx counts as delivered. Anything else, a 3xx redirect, a 4xx, a 5xx, a dropped connection or a timeout, counts as a failure and gets retried.

Retries are why at-least-once is the right mental model when you write the handler. Running it twice with the same webhook-id should have the same effect as running it once. Store the id, check whether you have seen it before, and only then do the work.

How OneLifeVibe uses it

Webhook delivery on the OneLifeVibe developer platform is at-least-once. Every attempt for a given event repeats the same webhook-id value, so one dedupe check on that header covers a retry and any duplicate that turns up later.

Answer 2xx quickly. Write the event down, hand the real work to a background job, and return. A handler that calls three other services before it responds spends that time inside the delivery attempt, and a slow answer comes back as a failed delivery.

Webhooks from OneLifeVibe are signed, so check the signature before you act on the body.

Common mistakes

Returning 200 to silence the retries. If your processing broke, a 5xx is the honest answer and the retry is what saves the event. A cheerful 200 throws it away.

Deduping on the body instead of the header. The webhook-id header is the identity of the event. A hash of the payload is not, and it will eventually collide with something it should not.

Assuming exactly-once, then wondering why you sent the same receipt twice. Assume duplicates, make the handler idempotent, and the second copy becomes a no-op instead of a support ticket.

Questions

Why am I receiving the same webhook event twice?

Delivery is at-least-once, so a retry can arrive alongside an earlier attempt that was slow or did not return 2xx. Both carry the same webhook-id, so dedupe on that header and the second copy does nothing.

What should my webhook endpoint return?

Return a 2xx as soon as you have stored the event safely. Anything else is a failure and is retried, including redirects, 4xx responses, 5xx responses and timeouts.

See it working. The OneLifeVibe connector and Platform API put these pieces together.

Get a free key Read the docs

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.