Authentication
The X-API-Key header, where keys come from, and the 401/402 rows it can return.
#The X-API-Key header
Every request carries one header:
X-API-Key: YOUR_API_KEYNo OAuth flow, no token exchange, no expiry to track - the key you generate is the credential you send, on every call, until you revoke it. Keys are created and rotated at https://app.up2data.ai.
Warning
Never expose a key in client-side code, a public repository, or a URL. Anyone holding it can spend your credits.
Multiple keys can be active on the same account at once, so rotation never means downtime: create a new key, deploy it, then revoke the old one. Revocation takes effect within 60 seconds - keys are cached briefly, so the old key can keep working for a few more seconds after you revoke it.
#Example call
curl -X POST https://api.up2data.ai/v1/profiles/enrich \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://linkedin.com/in/satyanadella"}'#When a key fails
| Status | Type | Meaning |
|---|---|---|
| 401 | invalid_api_key |
Missing, malformed, or revoked key |
| 402 | insufficient_credits |
The key is valid, but your balance cannot cover this call |
{
"error": {
"type": "invalid_api_key",
"message": "The API key provided is invalid or has been revoked.",
"requestId": "req_1n4kd02p"
}
}