Glossary

webhook-timestamp

webhook-timestamp is a Unix seconds header that OneLifeVibe includes in the signed string, so you can reject old deliveries.

Updated November 12, 2026

At OneLifeVibe

Related terms

What it means

A webhook timestamp is the time a delivery was sent, written as Unix seconds: the number of seconds since 1 January 1970 UTC. It travels as an HTTP header alongside the signature.

On its own the header proves nothing. Anyone who can reach your endpoint can send a timestamp. It only becomes useful when the sender puts it inside the string that gets signed, which ties the time to the payload and the secret.

That is what webhook-timestamp means in a signed delivery: a value you check for freshness and feed into the signature calculation, not a field you read and trust by itself.

How it works

The sender builds a signing string from the timestamp and the request body, computes an HMAC with a shared secret, and sends the result in a signature header. The receiver repeats the calculation with its own copy of the secret and compares the two.

Replay protection comes from the freshness check. Your endpoint reads webhook-timestamp, compares it with its own clock, and rejects anything outside the tolerance you set. A captured request that once verified stops working after that window closes.

Order matters. Reject stale timestamps first, then verify the signature. Both checks are cheap, and a request that fails either one should not reach your business logic.

How OneLifeVibe uses it

Every OneLifeVibe delivery is a POST with three signed headers: webhook-id, which is the event id, webhook-timestamp in Unix seconds, and webhook-signature. Two more headers carry context: x-olv-event and x-olv-world.

The signature is v1= followed by the lowercase hex HMAC-SHA256 of the string {webhook-timestamp}.{raw body}, keyed with the endpoint secret as UTF-8 text. A dot separates the timestamp from the body. The body is the raw request body, exactly as it arrived. The endpoint secret is returned once, when the subscription is created, and it is not shown again.

Deliveries are at-least-once, so the same event can arrive more than once. Dedupe on webhook-id. Use webhook-timestamp for the freshness check: an old delivery whose signature still verifies should be dropped rather than processed.

Common mistakes

The most common failure is signing the parsed body instead of the raw bytes. If your framework parses the request and you re-serialize it, key order and whitespace can change and the HMAC will not match. Read the raw body, verify, then parse.

The second is leaving the timestamp out of the signed string. Hashing only the body gives you a signature that can be replayed with a fresh timestamp header, and OneLifeVibe signatures will never match your calculation.

Other ones: treating the value as milliseconds, comparing hex signatures case-sensitively, and using webhook-id as replay protection when it exists for deduplication. Save the endpoint secret at creation time, because verification is impossible without it.

Questions

Is webhook-timestamp in seconds or milliseconds?

Unix seconds. OneLifeVibe sends the number of seconds since 1 January 1970 UTC and uses that exact string, with a dot before the raw body, as the input to the HMAC-SHA256.

How do I verify a OneLifeVibe webhook?

Take the webhook-timestamp header, add a dot and the raw request body, then compute HMAC-SHA256 with the endpoint secret as UTF-8 text. Compare the lowercase hex to the value after v1= in webhook-signature, and reject the delivery if the timestamp is stale or the values differ.

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.