SupplyChainNode.asi
The canonical domain of the advertising system, such as an SSP, exchange, or header wrapper, that bidders connect to for this hop. It should match the domain used for that system in ads.txt files. Required.
Field facts
- Path
source.schain.nodes.asi- Object
- SupplyChainNode
- Type
- string
- Requirement
- Required
- Added
- OpenRTB 2.6-202204
- Spec section
- 3.2.26
How it is used
Use the bare, lowercase domain that hosts the system's sellers.json, without scheme, path, or port. Some systems use an operational domain that differs from the corporate one, which helps WHOIS and reverse IP lookups. Whichever you pick, use the same string in ads.txt, sellers.json, and every node you append.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"source": {
"schain": {
"nodes": [
{
"asi": "exchange.example"
}
]
}
}
}Common mistakes
- Sending a full URL such as https://exchange.example/ssp instead of the bare domain (
openrtb.schain.node.asi_not_domain). - Mixed case such as Exchange.example breaks string matching against ads.txt (
openrtb.schain.node.asi_not_lowercase). - An empty string passes a type check but identifies nothing. The validator reports it as an error.
Version history
Added in OpenRTB 2.6-202204, and present in the latest snapshot. The table shows how each version's spec text types the field.
| Versions | Type in the spec | Required | Deprecated |
|---|---|---|---|
| 2.6-202204 | Added in the first 2.6 release, published without a structured text archive; the 2.6-202210 republication is the first tagged text. | ||
| 2.6-202210 to 2.6-202606 | string | Yes | No |
Related fields
Other SupplyChainNode fields
For a walkthrough of the whole object, read Supply chain (schain).