No bid and errors
| Status | Meaning | Body |
|---|---|---|
200 | Elo bids. | A bid response. |
204 | No bid. | Empty. |
400 | The body is not a native bid request. | Empty. |
401 | The API key is missing or wrong. | JSON with a detail message. |
204: no bid
Section titled “204: no bid”A 204 is a normal answer. Elo does not say why it did not bid, but these
causes are ones you can act on:
| Cause | What to do |
|---|---|
| Bidding is not turned on for your publisher. | Ask Elo to turn it on. Until then only test requests get a bid. See Onboarding. |
| You sent more requests per second than your request rate limit. | Keep your traffic under the limit Elo gave you when it turned bidding on. |
| The request has no context to match. | Send keywords, intent, categories or a content title, in the standard fields or in imp[0].ext.elo. See Context. |
| Elo could not price the request in time. | Send a tmax of 1000 ms or more. See Timing. |
| The request has no country. | Send device.geo.country. |
imp[0].bidfloor is above Elo’s price, or bidfloorcur is not USD. | Send floors in USD. |
| A required asset is one Elo does not answer, such as video. | Mark it optional. See Native request. |
regs.coppa is 1. | None. Elo does not bid on inventory directed at children. |
Elo also does not bid when no campaign fits the request.
400: not a bid request
Section titled “400: not a bid request”Elo answers 400 when the body is not a native bid request:
- the body is not JSON, or has no
id; impis missing or empty;imp[0]has nonativeobject;imp[0].native.requestis not valid JSON, or has no assets.
401: wrong key
Section titled “401: wrong key”{ "detail": "Invalid publisher API key" }A request with no key gets { "detail": "Publisher API key required" }.
Check that the Authorization header is Bearer followed by your publisher
API key, which starts with elo_pub_.