Glossary
endpoint secret
An endpoint secret is the per-endpoint HMAC key OneLifeVibe uses to sign webhook deliveries. You get it once, when the subscription is created.
Updated November 15, 2026
- Also called
signing secret
At OneLifeVibe
- Each OneLifeVibe delivery carries webhook-id, webhook-timestamp (Unix seconds) and webhook-signature: v1= followed by the hex HMAC-SHA256 of "{timestamp}.{raw body}" with the endpoint secret. The secret is returned once, when the subscription is created.
- webhook-signature is v1= followed by the lowercase hex HMAC-SHA256 of "{webhook-timestamp}.{raw body}", keyed with the endpoint secret as UTF-8 text. The secret is returned once, when the subscription is created.
Related terms
What it means
An endpoint secret is a string tied to one webhook endpoint. OneLifeVibe uses it as the HMAC key when signing deliveries to that endpoint, so the receiver can check that a delivery was signed with that secret and that the body was not changed in transit. People also call it a signing secret.
It is not a password you type into a login form or a token you send with each API call. It stays on your server and in your verification code. The value matters as UTF-8 text, so store the exact characters OneLifeVibe returned.
How it works
Webhooks are HTTP requests. HMAC-SHA256 takes a message and a key and produces a fixed-length digest. OneLifeVibe builds the message from the webhook-timestamp header, a dot, and the raw request body: {webhook-timestamp}.{raw body}. It signs those bytes with the endpoint secret, turns the digest into lowercase hex, and sends it in webhook-signature with a v1= prefix.
On your side, read the three headers: webhook-id, webhook-timestamp, and webhook-signature. Rebuild the same string from the timestamp and the raw body, hash it with your stored secret, and compare your v1= value to the header. Use the bytes you received before any parser, framework middleware, or proxy changes them. If the values differ, reject the delivery and do not process the payload.
How OneLifeVibe uses it
Each endpoint secret belongs to one endpoint and is returned when the subscription is created. OneLifeVibe shows it once. Copy it into your secret store at that point; your handler needs it later to verify deliveries.
Every delivery carries webhook-id, webhook-timestamp in Unix seconds, and webhook-signature. The signature value is v1= followed by the lowercase hex HMAC-SHA256 of "{webhook-timestamp}.{raw body}", keyed with the endpoint secret as UTF-8 text. The webhook-id travels with the delivery, but the signed string is the timestamp, a dot, and the raw body. Verify against that exact construction, not a variant.
Common mistakes
The usual failure is computing the HMAC over a different body than the one that arrived. Frameworks often parse the request and hand you an object, then re-serialize it. Whitespace, key order, or escaping can change and the HMAC will not match. Keep the raw body bytes for verification.
Another mistake is putting v1= or the webhook-id into the hash input. The digest covers only {webhook-timestamp}.{raw body}, with the secret as the key. Use the timestamp header exactly as sent, use lowercase hex, and compare the full header value. If verification fails, return an error and skip processing. Do not fall back to trusting the payload because the check was inconvenient.
Questions
How do I verify a OneLifeVibe webhook signature?
Read webhook-timestamp and webhook-signature, then compute HMAC-SHA256 over "{webhook-timestamp}.{raw body}" using your endpoint secret as UTF-8 text. Format your digest as v1= plus lowercase hex and compare it to the header. If it does not match, reject the delivery.
What does the webhook-timestamp contain?
It contains Unix seconds. It is part of the signed string, so use the header value exactly as received when you recompute the HMAC. Do not replace it with your server's current time.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.