HTTP headers
Request header
Our OpenRTB An open industry standard for communication between buyers and sellers of online advertising in real-time bidding auctions. It's published by the IAB. bidding API uses HTTP 1.1 protocol and sends the following request headers:
Attribute | Scope | Description |
---|---|---|
Connection
|
Required | The connection type for the request. We accept "Keep-Alive ". |
Content-Length
|
Required | The size of the request. |
Content-Type
|
Required | The content type for the request. This value is always "application/json ". |
Host
|
Required | The domain of the bidding URL. |
x-openrtb-version
|
Required |
The version of OpenRTB protocol used for the request. Index defaults to sending Note: While we send |
|
Required |
Specifies that the payload in the request body utilizes gzip compression. For more information about gzip, see Send and receive compressed traffic using gzip. |
Response header
The Index OpenRTB bidding API uses HTTP 1.1 protocol and sends the following response headers:
Attribute | Scope | Description |
---|---|---|
|
Optional |
Specifies the size of the response. |
|
Optional |
The connection is closed after processing the request if the value is " |
No-bid signal
To express a "no-bid", you may return an empty bid response An OpenRTB response that is sent by the DSP in response to the SSP's or ad exchange's bid request. It is an event directed back to the seller expressing a valuation for the request and conditions of sale. with HTTP Status Code 204 "No Content"
.