Native 1.0

Objects: 14
Fields: 60

This version's data comes from an OCR transcript of the official legacy PDF, reviewed table by table before ingestion, and is in draft status; audit fixes and faithfully kept official quirks are registered in the object notes and provenance record.

Bid Request side (§4)

Native Markup Request§4.1	7 fields1 required	The Native Object defines the native advertising opportunity available for bid via this bid request. It must be included directly in the impression object if the impression offered for auction is a native ad format. The Default column dictates how optional parameters should be interpreted if explicit values are not provided.
Asset Request§4.2	7 fields1 required	The main container object for each asset requested or supported by Exchange on behalf of the rendering client. Any object that is required is to be flagged as such. Only one of the {title,,img,video,data} objects should be present in each object. All others should be null/absent. The id is to be unique within the AssetObject array so that the response can be aligned.
Title Request§4.3	2 fields1 required	The Title object is to be used for title element of the Native ad.
Image Request§4.4	7 fields	The Image object to be used for all image elements of the Native ad such as Icons, Main Image, etc.
Video Request§4.5	5 fields4 required	The video object to be used for all video elements supported in the Native Ad. This corresponds to the Video object of OpenRTB 2.3. Exchange implementers can impose their own specific restrictions. Here are the required attributes of the Video Object. For optional attributes please refer to OpenRTB 2.3.
Data Request§4.6	3 fields1 required	The Data Object is to be used for all non-core elements of the native unit such as Ratings, Review Count, Stars, Download count, descriptions etc. It is also generic for future of Native elements not contemplated at the time of the writing of this document.

Bid Response side (§5)

Native Ad Creative JSON§5.1	1 fields1 required	The JSON returned in adm or in response to nurl is a JSON string with the following attributes:
Native Response§5.2	6 fields2 required	The native object is the top level JSON object which identifies a native response. The native object has following attributes
Asset Response§5.3	8 fields1 required	Corresponds to the Asset Object in the request. The main container object for each asset requested or supported by Exchange on behalf of the rendering client. Any object that is required is to be flagged as such. Only one of the {title,img,video,data} objects should be present in each object. All others should be null/absent. The id is to be unique within the AssetObject array so that the response can be aligned.
Title Response§5.4	2 fields1 required	Corresponds to the Title Object in the request, with the value filled in.
Image Response§5.5	4 fields1 required	Corresponds to the Image Object in the request. The Image object to be used for all image elements of the Native ad such as Icons, Main Image, etc.
Data Response§5.6	3 fields1 required	Corresponds to the Data Object in the request, with the value filled in. The Data Object is to be used for all miscellaneous elements of the native unit such as Ratings, Review Count, Stars, Downloads, Price count etc. It is also generic for future of Native elements not contemplated at the time of the writing of this document.
Video Response§5.7	1 fields1 required	Corresponds to the Video Object in the request, yet containing a value of a conforming VAST tag as a value.
Link Response§5.8	4 fields1 required	Used for 'call to action' assets, or other links from the Native ad. This Object should be associated to its peer object in the parent Asset Object or as the master link in the top level Native Ad response object. When that peer object is activated (clicked) the action should take the user to the location of the link.

Enumerations Official samples