XSD Schema Files
The XSD files are available at http://adgear.com/api_schemas/xml/ - you may choose to download them, or reference them live.
They are divided into the following:
- The INPUT namespace "http://adgear.com/api/schemas/xml#input":
- Every root element is defined in a dedicated XSD
- All the root elements are available in a combined all_input.xsd
- The OUTPUT namespace "http://adgear.com/api/schemas/xml#output":
- Every root element is defined in a dedicated XSD
- All the root elements are available in a combined all_output.xsd
- Both all_input.xsd and all_output.xsd are available in a combined all.xsd
You may choose to use a single XSD for the particular element you will be consuming or receiving, or any of the higher combined XSDs. You may also choose not to use XSDs at all and dynamically process and emit the XML elements.
AdGear is strict in what it emits and liberal in what it accepts. Any XML response emitted by AdGear should validate against the expected root element for the API end point. Any XML request received by AdGear is checked only for well-formedness, and is not validated against the published input XSD.
Individual element documentation
The HTML version of the schema's annotations is available at http://adgear.com/api_schemas/xml/_doc/, and is considered the most exhaustive source for the inputs and outputs when calling AdGear's API end points.
JSON users should also reference the above XML schemas and documentation, and adapt appropriately from XML to JSON while keeping the entity structure the same.
Note
It is worth noting that the same element name is often defined in both the input as well as the output namespaces. For example, when creating a new advertiser, the submitted root element "advertiser" needs to conform to the "advertiser" element in the input schema, while the returned "advertiser" root element from AdGear will conform to the "advertiser" element in the output schema. There are, of course, similarities between the two, but there are also differences.