Overview
BidMachine bidding supports the OpenRTB 2.5 protocol to receive bid requests from supply partners and return bid responses. To integrate with BidMachine, partners must use the BidMachine SDK and ensure their bid requests comply with the OpenRTB 2.5 specification.
Protocol
- Transport:
HTTP
- Security: TLS 1.2 or higher is recommended
Request Regions
BidMachine servers are hosted in three regions to minimize latency:
- US
- EU
- APAC
We recommend using the region endpoint closest to your infrastructure.
Endpoint
After agreement on this specification, BidMachine will provide a custom endpoint for your RTB calls.
Supported Ad Formats
BidMachine participates exclusively in mobile in-app auctions. Supported ad formats:
- Fullscreen Banner: 320×480, 480×320, 768×1024, 1024×768
- Small Banner: 320×50, 728×90
- Skippable Video: 320×480, 480×320, 768×1024, 1024×768
- Rewarded Video: 320×480, 480×320, 768×1024, 1024×768
- Native Ads
Supported Currency
USD
only
Supported Auction Type
- First-price auction only
Bid Request Requirements
Each bid request must contain exactly one imp
object. Key OpenRTB fields:
app.bundle
(required)app.storeurl
(required)app.name
(required)imp.instl
(required)device.os
(required)tmax
(required; recommended>1000
ms)
For a complete Bid Request specification, see the BidMachine OpenRTB Bid Request Spec.
- Partners should share a sample bid request they plan to use for integration.
- If you have a custom bid request spec, please contact your BidMachine Account Manager.
Bid Response
BidMachine’s bid response follows the OpenRTB 2.5 protocol.
No-Bid Response
To indicate no-bid, return an empty response body with HTTP status code 204
.
Win/Loss Notifications
- Provide both win (
nurl
) and loss (lurl
) notification URLs in your bid response. - Use the appropriate loss codes as defined by OpenRTB.
- If you require custom auction macros in your notification URLs, notify your BidMachine Account Manager.
For sample request and response payloads, see the Response and Request Examples.