Death Verification API
Create and manage API keys
Create Live and Test keys, set an expiry and IP allowlist, and store keys safely.
Last updated October 8, 2026
Plan: Death Verification API · For: Developers · Time: 3 min read
Once our team has set up your account, you create and manage your own API keys.
Live and Test keys
| Key | Prefix | What it does |
|---|---|---|
| Live | om_live_ | Searches real data and counts against your lookup allowance |
| Test | om_test_ | Returns fixed sample responses. No real search, and it doesn't use your allowance |
The key types are explained at the top of the page (callout 1).
Create a key
- In the sidebar, select API Keys.
- Enter a New key name, such as "Production" or "Staging" (callout 2).
- Choose Live or Test (callout 3).
- Optional: in Expires in (days), set how long the key lasts. Leave it as Never for no expiry (callout 4).
- Optional: in IP allowlist, enter the IP addresses or ranges your servers call from, separated by commas (callout 5). Calls from anywhere else are refused.
- Select Generate key (callout 6).
- Copy the key right away. It's shown only once.
You can have up to 10 active keys.
Store keys safely
- Put keys in a secrets manager or an environment variable, not in your source code.
- Don't share keys in email or support cases.
- Use separate keys for production and testing, so you can revoke one without affecting the other.
Rotate or revoke a key
- Create a new key and deploy it.
- Revoke the old key on API Keys.
Troubleshooting
- **
key_expired**: create a new key. - **
ip_not_allowed**: the call came from an IP address that isn't on the key's allowlist. Add it, or create a key without an allowlist. - **
unauthorized**: check theAuthorization: Bearerheader and that you copied the whole key.
Related
Was this article helpful?