Enrich many OpenRTB bid requests in one call

post

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

An array of OpenRTB 2.6 bid requests in; an array of passthrough responses out,
same order, one-to-one. An invalid item occupies its slot with the {code, message} error object its single-request 400 would have carried — the one
sanctioned non-OpenRTB element in this route's 2xx responses — while valid 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
query parameters; no latency SLA on batch. Per-item diagnostic signaling on this route
is provisional — a batch caller that needs a per-item outcome, confidence, or
reason should use the parameterized lookup batch, whose envelope carries them.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

200Batch processed; inspect each slot for the per-item outcome — an enriched or unchanged bid request, or an error object for an invalid item.

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), a non-null ext.pixalate that is not itself an object, 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.