Authentication

All requests are authenticated with an API key passed in the X-API-Key header:

curl https://api.up2data.ai/v1/account \
  -H "X-API-Key: u2d_live_..."

Key types

Prefix	Environment	Behavior
`u2d_live_`	Production	Real scrapes, real credits.

Keys are created in the dashboard. To verify Signal webhook plumbing without spending credits, use POST /v1/signals/{id}/test-webhook.

Creating and rotating keys

Keys are managed in the dashboard. You can hold multiple active keys per account, which makes zero-downtime rotation straightforward:

Create a second key

Both keys are live simultaneously — same account, same credit balance.

Deploy the new key

Roll it out across your services at your own pace.

Revoke the old key

Revocation is immediate. Any request with the old key returns 401.

Failure modes

Status	`error.type`	Meaning
`401`	`invalid_api_key`	Missing, malformed, or revoked key.
`402`	`insufficient_credits`	Key is valid but the balance can’t cover the call.

401 response

{
  "error": {
    "type": "invalid_api_key",
    "message": "The API key provided is invalid or has been revoked.",
    "requestId": "req_1n4kd02p"
  }
}

Never expose keys in client-side code, public repos, or URLs. If a key leaks, revoke it in the dashboard — rotation takes effect instantly.

Getting started

CLI & MCP

Concepts

Key types

Creating and rotating keys

Failure modes

​Key types

​Creating and rotating keys

​Failure modes

Key types

Creating and rotating keys

Failure modes