Jobs & Batch Processing

When to use jobs

• High-throughput or batched verification where per-item latency is not critical.
• Long-running checks that may require external fetching or multi-step processing.
• Workflows that benefit from retry/backoff patterns and centralized job monitoring.

Submit a batch

POST /v1/verify-claims-batch accepts multiple claims in a single request. The endpoint typically responds with a job_id you can poll for completion.

Behavior and fields may vary by implementation; treat the job_id as an opaque identifier and persist it for later polling.

Polling jobs

Use GET /v2/jobs/{job_id} to retrieve job status and results.

{"job_id":"88ac79...","status":"queued"}

Tips

• Use idempotency keys where supported to avoid duplicate processing on retries.
• Retry transient failures with exponential backoff and a capped retry count.
• Cache or persist completed job results to avoid unnecessary polling.