Authentication

Every request is authenticated with an API key in the Authorization header:

curl "https://api.scrapersocial.com/v1/me" \
  -H "Authorization: Bearer sk_live_..."

Keys start with sk_live_ and are shown once at creation — store them in a secrets manager, not in source control.

Managing keys

Create, name, and revoke keys at scrapersocial.com/app/keys. You can hold several keys at once (one per environment or service), and revoking one takes effect within seconds.

Checking who you are

/v1/me returns the account attached to the key — useful in CI to verify a secret is wired correctly:

{
  "data": {
    "account_id": "acc_01J...",
    "plan": "annual",
    "credits_remaining": 11310,
    "rate_limit_rpm": 300
  },
  "request_id": "req_01JZX4M8Q2TE9W"
}

Failure modes

Status	Code	Meaning
401	unauthorized	Missing or malformed Authorization header
401	invalid_key	Key revoked or unknown
402	insufficient_credits	Balance is empty — top up or upgrade

For OAuth-based agent access (the MCP server supports OAuth 2.1 with PKCE), see For AI agents.

Next: Errors · Rate limits