Infrastructure API (Queues)
Who should read this — Integrators triggering batch jobs and metadata sync via Cloudflare Queues. See API overview for authentication.
Overview
Section titled “Overview”API for creating batch jobs and triggering metadata synchronization using Cloudflare Queues.
Base path: /api/v1/queues
Endpoints
Section titled “Endpoints”POST /api/v1/queues/research
Section titled “POST /api/v1/queues/research”Research discovery (URL processing) batch creation.
Request body: country, category, urls (1–10000), chunkSize (optional, default 100).
POST /api/v1/queues/liveness
Section titled “POST /api/v1/queues/liveness”Liveness (domain survival) check batch creation.
Request body: country, domains (1–10000), chunkSize (optional, default 50).
POST /api/v1/queues/contract
Section titled “POST /api/v1/queues/contract”Contract (Seed contract) creation batch.
Request body: country, category, domainIds (1–1000), chunkSize (optional, default 20).
GET /api/v1/queues/batch/:batchId
Section titled “GET /api/v1/queues/batch/:batchId”Retrieve status (or result) of a specific batch ID.
POST /api/v1/queues/trigger/metadata-sync
Section titled “POST /api/v1/queues/trigger/metadata-sync”Metadata synchronization trigger.
Authentication
Section titled “Authentication”Send API credentials in the Authorization header. See API overview.
Next steps
Section titled “Next steps”- Seeds, Research & Health API — Core engine endpoints.
- JSON structure design — Output schema reference.