Resolve many lookups in one call

post

https://epg-api.pixalate.com/v1/lookup/batch

An array of lookup requests in; an array of lookup responses out, same order,
one-to-one. Each item carries its own timestamp, so an impression log enriches
against the schedule as of each impression, and its own verbose. An invalid
item gets an error entry in its slot while the other items resolve normally.
Exceeding the documented item cap fails the whole batch with 400. Each item counts
as one unit against your rate limit and your usage. No latency SLA on batch.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

200Batch processed; inspect each slot for the per-item outcome.

400Malformed request — a non-conforming body, a missing or empty required field, a read field of the wrong type, a timestamp violation (unparseable, more than 5 minutes in the future, or older than the 7-day window), an out-of-vocabulary os, or an exceeded batch cap.

401Missing or unknown credential.

403Known credential without entitlement to this product.

413The batch body exceeded the maximum number of bytes the route reads. The item cap bounds how many items a batch may carry; this bounds how large those items may be in total, and the two are enforced independently. Split the batch and retry.

429Rate limit exceeded. Retry-After says when the window clears.

503Serving infrastructure degraded — the API fails closed and never masquerades as a data miss. Retry after the indicated delay.