Skip to content
EN
Get API key
Browse documentation

Get started

Rate limits and usage

Inspect account capacity, respond to rate limits and track completed work.

On this page

Check your limits

Limits follow your account and plan. Run this free check with the key that will submit the work; all keys on the account share the same capacity.

Use your saved CLI access. For a named profile, append --profile NAME to each command. These reads do not spend query credits.

Free account reads
flashdata account limits

Understand each limit

Start with one in-flight request, then increase within reported limits. HTTP read endpoints and trial registration also have their own rate limits; these capacity fields are not requests-per-minute quotas.

FieldMeaning
limits.concurrencyPlan ceiling for simultaneous work, not a count of free slots.
limits.batchSizeMaximum items in one batch submission.
limits.pendingJobsMaximum pending jobs for the account.
current.pendingJobsPending count at the time of the read. It can change before submission.

Handle a 429 response

Read the error body and Retry-After header. To inspect a free account read, run this in a Bash terminal where FLASHDATA_API_KEY is set. Headers are written to limits-headers.txt and the response to limits.json.

Capture status, headers and body · Bash / cURL
curl --silent --show-error --max-time 20 \
  --header "X-API-Key: ${FLASHDATA_API_KEY:?Set FLASHDATA_API_KEY first}" \
  --dump-header limits-headers.txt --output limits.json \
  --write-out 'HTTP %{http_code}\n' \
  https://api.flashdata.dev/v2/api-access/limits
cat limits-headers.txt limits.json

Wait before retrying

This example means wait at least 60 seconds. Retry-After can also be an HTTP date. Use the returned value, not a fixed delay.

Illustrative response headers
HTTP/1.1 429 Too Many Requests
Retry-After: 60

Choose the next action

SituationAction
Capacity fullReduce concurrency or wait for pending jobs to finish.
No Retry-AfterUse capped backoff with jitter and a finite retry limit.
Registration limitedWait, then retry with the same profile, input and proof. Do not switch IPs.
Submission timed outInspect the existing run or job before resubmitting; its outcome is unknown.

Read account usage

The default window is the last seven days. Usage covers all account keys, restricted to the sources this key can access.

Use your saved CLI access. For a named profile, append --profile NAME to each command. These reads do not spend query credits.

Free account reads
flashdata account usage

Check completed work and credits

Read totals and bySource, then compare from and to with your task records. CLI JSON wraps the response in data. Recent requests or refunds can take time to appear, even when updating is false.

Illustrative response excerpt
{
  "scope": "account_authorized_sources",
  "unit": "Credits",
  "totals": {
    "requests": 5,
    "completed": 5,
    "failed": 0,
    "credits": 0.1
  }
}

Filter a source and date range

Replace the UTC dates with your reporting period, up to 31 days. from is inclusive and to is exclusive; both are rounded down to minutes. This reads existing usage only.

Example reporting window
flashdata account usage --source google_search --from "2026-11-01T00:00:00Z" --to "2026-11-04T00:00:00Z"