Glossary
expiry
Expiry is a set time after which a key stops working. OneLifeVibe keys can carry an expiry, and a passed one is refused.
Updated November 15, 2026
- Also called
expiration
At OneLifeVibe
- 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.
- The key carries an expiry date and that time has passed.
Related terms
What it means
Expiry, also called expiration, is a set time after which something stops working. For a credential such as an API key, it is a stored timestamp that the server compares with the current time. Before that time, the credential can still be accepted. After it, the credential is refused.
Expiry is not the same as revocation. Revocation is a separate state that can be set on a credential. A key can have an expiry date, a revocation state, or both, and OneLifeVibe checks them at different points. The related term here is API key.
How it works
On each request, the server has to identify the credential before it can evaluate an expiry. That means a credential with the wrong shape or an unknown value fails before any time comparison happens. A known credential also has to pass a secret check first in systems that store a hash instead of the secret itself.
OneLifeVibe follows this order: shape, existence, hash, expiry, revocation, client status, plan. The expiry check sits fourth. It only runs after the key has the expected shape, exists, and its secret matches the stored SHA-256 hash. If any of those earlier checks fail, the request is refused without the expiry being reached.
That order matters when you debug a refused key. If the client sends an old secret after a rotation and the key's expiry has also passed, the request fails at the hash step, not the expiry step. Fix the secret first, then see whether the expiry is still a problem.
How OneLifeVibe uses it
OneLifeVibe keys can carry an expiry date. When that time has passed, the key is refused. The check is part of the same ordered sequence: shape, existence, hash, expiry, revocation, client status, plan. Expiry comes after the hash check and before revocation, client status and plan.
The practical result is that an expired key does not skip ahead. If the key has the wrong shape, does not exist, or its secret does not match the stored SHA-256 hash, the request stops earlier. A key that passes those three checks and whose expiry time has passed is refused at the expiry step, and the later checks are not reached.
Use expiry when a key should stop working at a known time. Keep the expiry value with the key record in your own system so you can see it during rotation or debugging. When a request is refused, confirm the key shape, existence and secret hash before you spend time on the expiry date.
Common mistakes
The first mistake is assuming expiry is checked first. It is fourth. A malformed key, an unknown key or a secret that does not match the stored SHA-256 hash stops the request before the expiry is considered.
The second is treating expiry and revocation as the same switch. They are separate checks, and revocation comes after expiry. A key can be refused at either step.
The third is losing track of which key has which expiry. If you rotate a secret but keep an old expiry date, the key can stop working sooner than you expect. Record the expiry in your own records, and check the earlier steps before you change the date.
Questions
What happens when a OneLifeVibe key expires?
When the key's expiry time has passed, the key is refused. That refusal happens at the expiry step, after the key passes the shape, existence and hash checks. If an earlier check fails, the request stops before expiry is evaluated.
Does OneLifeVibe check expiry before the secret hash?
No. The order is shape, existence, hash, expiry, revocation, client status, plan. A secret that does not match the stored SHA-256 hash fails at the hash step, so the expiry check never runs for that request.
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.