Live backend health and capacity

Whether the live-scrape backends are up, how much capacity they have, and what the batch limits are. Poll this before a large job and back off on `degraded` rather than discovering it through 502s.

This is a catalog read: it is served from the CRM Solid database in milliseconds, costs one budget unit, and reports how old the reading is in meta.cache_age_s. It needs the scrape:live scope (Live scrape): Read from the platform itself rather than from the catalog: a profile or channel on any of the seven platforms, and on X the whole content layer - timelines, posts, replies, quotes, threads, followers, search, lists and communities.

curl "https://crmsolid.com/data-api/v2/scrape/status" \
  -H "Authorization: Bearer psk_live_..."

const res = await fetch("https://crmsolid.com/data-api/v2/scrape/status", {
  headers: {
    Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
  },
});

if (!res.ok) {
  const { error } = await res.json();
  throw new Error(`${error.code}: ${error.message} (${error.request_id})`);
}

const { data, meta } = await res.json();

import os

import requests

res = requests.get(
    "https://crmsolid.com/data-api/v2/scrape/status",
    headers={"Authorization": f"Bearer {os.environ['CRM_SOLID_DATA_API_KEY']}"},
    timeout=30,
)
res.raise_for_status()

payload = res.json()
data, meta = payload["data"], payload["meta"]

Keys look like psk_live_... for production keys, psk_test_... for test keys and are minted in the panel.

State

operational

Backends

2 items

Budgets

2 items

Limits batch max handles

25

Limits batch concurrency

5

Limits x cache ttl s

60

Limits x pool concurrency

4

{
  "data": {
    "state": "operational",
    "backends": [
      {
        "name": "xlookup",
        "state": "up",
        "detail": "Serving from 4 authenticated account(s).",
        "metrics": {
          "ready": true,
          "accounts": 4,
          "uptime_s": 82140,
          "served": 19442,
          "errors": 118,
          "error_rate": 0.006,
          "cached_profiles": 812
        }
      },
      {
        "name": "telegram_bot",
        "state": "up",
        "detail": "Bot @playersells_bot is answering.",
        "metrics": {
          "bot": "playersells_bot"
        }
      }
    ],
    "budgets": [
      {
        "platform": "instagram",
        "per_minute": 10,
        "concurrency": 2,
        "available": 8,
        "in_flight": 1,
        "granted": 1204,
        "refused": 17
      },
      {
        "platform": "x",
        "per_minute": 20,
        "concurrency": 2,
        "available": 20,
        "in_flight": 0,
        "granted": 4881,
        "refused": 3
      }
    ],
    "limits": {
      "batch_max_handles": 25,
      "batch_concurrency": 5,
      "x_cache_ttl_s": 60,
      "x_pool_concurrency": 4
    }
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42
  }
}

• 401Unauthorizedunauthorized | invalid_key

  No key was presented, or the key is unknown, revoked or expired.

• 402PaymentRequiredpayment_required | subscription_inactive

  The key is valid but the plan behind it cannot serve the call: the included requests are spent and overage is switched off, capped or unfunded (payment_required), or the billing period lapsed and was not renewed (subscription_inactive). Retrying does not help; paying does. The X-Plan-* headers on this response say how far past the line you are.

  Carries X-Plan, X-Plan-Limit, X-Plan-Overage, X-Plan-Period-End, X-Plan-Remaining.

• 403Forbiddenforbidden_scope | forbidden_ip

  The key is valid but not allowed to make this call: it lacks the scope, or the request came from an address outside the key's allowlist.

• 422InvalidRequestinvalid_request

  A parameter is malformed, out of range or mutually exclusive with another. `details` names the offending fields.

• 429RateLimitedrate_limited | quota_exceeded

  Either the burst ceiling for the current minute or the daily quota is spent. Distinguish with the code: rate_limited clears within the minute, quota_exceeded does not clear until 00:00 UTC.

  Carries Retry-After, X-Quota-Limit, X-Quota-Remaining, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-Request-Id.

• 500InternalErrorinternal_error

  Something failed on our side. Internals are never leaked; quote the request id.

• 503Unavailableupstream_timeout | upstream_error | not_configured

  The request could not be served right now. BRANCH ON error.code, not on the status: 'upstream_timeout' means a source was too slow (this is what a catalog query hitting its 15-second statement timeout returns, so it is reachable from any endpoint that reads the corpus, not only the live-scrape ones) and the same call is worth retrying with backoff - narrowing it with a smaller limit, a filtered scope or a less popular account makes it far less likely; 'upstream_error' means a source was unreachable, so back off further; 'not_configured' means the capability has no backing service in this deployment, and retrying will never help.

Every response carries X-Request-Id and meta.request_id. Quote it in support requests.

This call only draws on the ordinary per-minute and per-day columns. Every response reports where you stand in X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and the X-Plan headers.

• GET/scrape/x/userLive X profile
• POST/scrape/x/usersLive X profiles, batched
• GET/scrape/instagram/userLive Instagram profile
• GET/scrape/telegram/channelLive Telegram channel read

Reference path: /data-api/reference/scrape-status