Account API

Two read-only endpoints for programmatic account introspection.

GET /v1/me

The account behind the key — handy for CI checks and dashboards:

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

{
  "data": {
    "account_id": "acc_01J...",
    "email": "dev@example.com",
    "plan": "annual",
    "credits_remaining": 11310,
    "credits_quota": 12000,
    "renews_at": "2027-07-01T00:00:00Z",
    "rate_limit_rpm": 300
  },
  "request_id": "req_01JZX4M8Q2TE9W"
}

GET /v1/usage

Usage records, newest first, paginated with cursor/limit. Filter with from/to (ISO dates) and endpoint:

curl "https://api.scrapersocial.com/v1/usage?from=2026-07-01&endpoint=/v1/tiktok/transcript" \
  -H "Authorization: Bearer sk_live_..."

{
  "data": [
    {
      "request_id": "req_01JZX4M8Q2TE9W",
      "endpoint": "/v1/tiktok/transcript",
      "credits": 8,
      "cache": "miss",
      "status": 200,
      "created_at": "2026-07-14T18:20:11Z"
    }
  ],
  "meta": { "count": 1, "has_more": false },
  "request_id": "req_01JZX51AB3CD4E"
}

Every metered response also carries live headers: X-Credits-Charged and X-Credits-Remaining, so most integrations never need to poll /v1/usage.

Related: Authentication · Rate limits