Integration

The Nimbus ad server is Open Real-Time Bidding (ORTB) version 2.5 compliant, however please review below as the spec has been optimized for communication performance around the Nimbus specific hybrid.

Endpoints

All requests to Nimbus are done via HTTP POSTs to submit RTB JSON bodies

Mobile

https://[ask_solutions_engineer].adsbynimbus.com/rta/v1

CTV

https://[ask_solutions_engineer].adsbynimbus.com/rta/ctv/v1 This endpoint can only be used to request video assets from Nimbus. This endpoint also allows for video ads to ad stitched together in an ad pod. Controls for ad podding can be requested VIA the video RTB extension object

Special Notes

Regarding underscores in property names: The OpenRTB spec itself is occasionally inconsistent when it comes to underscores. Nearly all properties in the spec are lowercase, not underscored. However, there’s are anti-patterns section in the spec that references a private_auction flag containing an underscore. The api_key, facebook_app_id, and session_id properties in our docs are both properties contained within Extension objects in the spec. As such, we include underscores in those properties as an anti-pattern to enable the reader to quickly distinguish custom fields from RTB specified fields. We’ve seen some demand partners take this approach as well and we favored it ourselves.