Run several sub-requests in one round trip
POST /batch · API key required
Fans out to routeSingle() per sub-request - same auth, rate-limit, and edge-cache pipeline as a normal top-level request, so batching cannot bypass per-resource auth or rate limits. Nested /batch sub-requests are rejected. The batch endpoint has its own (tighter) rate limit. Results always come back in request order; one sub-request failing never short-circuits the rest.
Request body
Content type: application/json
Responses
200- Per-item results, always in request order400429