Authorization header. Every request needs it.
Key format
Bavlio API keys start withbav_live_ followed by 43 URL-safe characters. The prefix lets you spot Bavlio keys in your secrets scanner. Treat the entire string as the secret.
Example
Creating a key
1
Sign in to bavlio.com
Use the Google or email account on your workspace. bavlio.com/login.
2
Open Settings → API keys
Free-tier accounts cannot create keys; upgrade to a paid plan if you see a 403 on creation.
3
Click Create key, name it, copy immediately
Name describes the use (
production-agent, staging-worker). The full value is shown only once on creation.4
Store it as a secret in your runtime
Set as
BAVLIO_API_KEY environment variable. Never commit it to source.Sending the key
Pass the key as a Bearer token. Both the SaaS API and the BaviMail proxy under/api/v1/bavimail/* accept the same header.
Rotating a key
1
Create the new key first
Both old and new keys are valid in parallel — no downtime.
2
Deploy your runtime with the new key
Update the secret in your environment, restart workers.
3
Verify traffic is on the new key
Look at the dashboard Last Used column for both keys.
4
Revoke the old key
Revoked keys return HTTP 401 on every subsequent request. There is no undo — create a new key if needed.
Scopes & permissions
x402 wallet auth (alternative)
AI agents without a Bavlio account can hit a subset of Bavlio’s data — email verification, email finder, LinkedIn URL discovery, prospect search — without an account, paying per call in USDC on Base mainnet via the x402 protocol. No signup, no API key, no subscription.x402 API Guide
Full guide to wallet-paid endpoints. 5 endpoints at 0.003-0.012 USDC each.
Quickstart
For agents using a regular
bav_live_ API key.