InMobi supplier ingest

InMobi also accepts OpenRTB supply from publishers, exchanges, and other supply partners. This profile covers those incoming requests and InMobi's responses, separate from the requests InMobi Exchange sends to DSPs.

Direction and version

Publishers and supply partners send bid requests to InMobi, and InMobi returns bid responses.

OpenRTB 2.5 JSON with 0 or 1 integer flags. Gzip compression is supported in both directions.

The RTBlint profile inmobi-supplier checks requests and responses against the published contract.

Rules beyond the OpenRTB spec

Each impression needs a placement identifier: a non-empty imp.tagid string or an integer imp.ext.placementid.
Requests need device with ua and lmt. The device table also marks ip, ipv6, and ifa required without describing fallbacks.
Requests need app or site inventory. The request guide describes app traffic, while InMobi's supplier FAQ supports both app and web.
Banner impressions need a positive w and h, directly or in a format entry. Video needs w, h, and mimes.
An impression may offer one banner, one video, or one of each.
The current supplier guide lists Audio, PMP, Deal, Metric, Data, and Segment as unsupported.
Inside imp.ext.skadn, sourceapp and skadnetids are required.

Documented extensions

Path	Meaning
`imp.ext.placementid`	Integer InMobi placement ID, an alternative to `imp.tagid`.
`imp.ext.skadn`	SKAdNetwork data with required `sourceapp` and `skadnetids`.
`imp.video.ext.rewarded`	1 for rewarded video.
`source.ext.omidpn`	Open Measurement partner name; `source.ext.omidpv` carries the version.
`regs.ext.gdpr`	GDPR flag in its legacy location.
`user.ext.consent`	TCF consent string in its legacy location.
`user.ext.eids`	Extended identifiers in their OpenRTB 2.5 location.
`device.ext.atts`	App Tracking Transparency status.
`device.ext.ifv`	iOS identifier for vendors.

What the validator checks for this profile

openrtb.profile.inmobi.banner_size_required InMobi supplier banners require positive w/h or a format with positive w/h.
openrtb.profile.inmobi.device_address The supplier guide labels both IP families required but does not define the alternative or privacy redaction behavior. Confirm address availability for this integration.
openrtb.profile.inmobi.inventory_required InMobi supplier ingest requires app or site inventory context; the current FAQ supports both directions.
openrtb.profile.inmobi.placement_required InMobi supplier ingest requires tagid or ext.placementid.
openrtb.profile.inmobi.supplier_unsupported The supplier request guide labels this object unsupported in its current version; negotiated integration support is not visible here.

Validate against this contract

Open the tester with the InMobi supplier ingest profile, or run:

rtblint validate --profile inmobi-supplier request.json