Glossary
SHA-256
SHA-256 is a one-way hash from FIPS 180-4. OneLifeVibe stores only a SHA-256 hash of each platform key, so a key is shown once and cannot be recovered.
Updated November 15, 2026
- Standard
- FIPS 180-4
- Also called
SHA256
At OneLifeVibe
- The platform stores only a SHA-256 hash, so a key is shown once and cannot be recovered: rotate by creating a new key and revoking the old one. Send it as Authorization: Bearer olvp_… or X-API-Key: olvp_….
- The key has the wrong shape, does not exist, or its secret does not match the stored SHA-256 hash. Keys are checked in this order: shape, existence, hash, expiry, revocation, client status, plan.
Related terms
What it means
SHA-256, also written SHA256, is a one-way hash function standardized in FIPS 180-4. You give it bytes and it returns a fixed-size digest. The same input always produces the same digest, and the digest does not reveal the input. A hash is not encryption: there is no key and no decrypt step.
OneLifeVibe uses SHA-256 for platform keys, which are API keys. The platform stores only a SHA-256 hash of each key. That lets it compare a presented key with the stored hash without keeping the original key. The related term is API key.
How it works
SHA-256 processes the input and produces a 256-bit value, usually shown as 64 hexadecimal characters. Change one byte of the input and the digest changes. Two different inputs are meant to produce different digests. You cannot take a digest and turn it back into the original bytes.
To check a secret, hash the presented value and compare that digest with the stored digest. If they match, the values match. If they do not match, the presented secret is not the one that produced the stored hash.
How OneLifeVibe uses it
OneLifeVibe stores only a SHA-256 hash of each platform key, so the key is shown once and cannot be recovered. If you lose it, create a new key and revoke the old one. That is the rotation path.
Send a platform key as Authorization: Bearer olvp_… or as X-API-Key: olvp_…. When a key arrives, OneLifeVibe checks it in this order: shape, existence, hash, expiry, revocation, client status, plan. At the hash step, the presented secret is compared with the stored SHA-256 hash. A wrong shape, a key that does not exist, or a secret that does not match the stored hash fails at that point.
Common mistakes
Do not treat SHA-256 as encryption or expect a hash to give the key back. OneLifeVibe cannot show an existing key again. Create a new key and revoke the old one instead of trying to recover the old secret.
Do not send a key in a different header or with a different prefix and expect it to pass. The accepted forms are Authorization: Bearer olvp_… and X-API-Key: olvp_…. Do not assume a key is valid because its shape looks right. Checks continue through existence, hash, expiry, revocation, client status and plan.
Questions
Can I recover a OneLifeVibe platform key if I lose it?
No. OneLifeVibe stores only a SHA-256 hash of each platform key, and the key is shown once. Create a new key and revoke the old one.
How do I send a OneLifeVibe platform key?
Send it as Authorization: Bearer olvp_… or as X-API-Key: olvp_…. OneLifeVibe checks shape, existence, hash, expiry, revocation, client status and plan in that order.
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.