Our AST API is continually changing. The vast majority of changes simply add new functionality, but occasionally we introduce breaking changes that may require you to adjust your integration.
This page explains what changes qualify as breaking changes to our AST API. It also gives examples of changes that do not qualify as breaking changes.
AppNexus reserves the right to fix bugs, adjust functionality to comply with our service policies and legal obligations, and change features and products in alpha and beta without providing early notice.
The following types of changes qualify as breaking changes:
Removal of or changing the name of a field in an event handler response (i.e. adObj api)
Removal of the object from an event handler callback function definition
Removal of or changing the name of an AST method (for example,
Modification of the data type of a field (E.g.: array of IDs converted to array of objects)
When we introduce a breaking change into our AST API, we will support the version of AST without the breaking change as the production (
Additionally, we will notify AST users of these changes and how to correctly reach each version during the breaking changes period.
The following types of changes do not qualify as breaking changes. Please note that this list is not exhaustive; these are just some examples of non-breaking changes.