Microsoft Advertising is introducing API versioning for new response fields and objects in the Campaign Management API.
With API versioning, the API returns additions based on the Api-Revision date included in the request. You no longer need to select versioned additions through AdditionalFields.
Existing AdditionalFields behavior remains unchanged unless the API documentation identifies a field or object as versioned.
For Microsoft Advertising SDK users
No action is required. Supported Microsoft Advertising SDKs automatically send the appropriate Api-Revision header with each request.
Upgrade to the latest supported SDK to access the newest versioned fields and objects.
For custom-client users
Include the following HTTP header with every REST or SOAP request:
Api-Revision: YYYY-MM-DD
Use a revision date published in the Microsoft Advertising API documentation.
Important considerations for generated proxies
Before using a later Api-Revision date, rebuild and test your proxy. An older proxy might not be able to deserialize fields or objects introduced after it was generated.
Don't use an arbitrary revision date. Use the revision date published in the API documentation.
Learn more
See the Microsoft Advertising API documentation for supported revision dates and information about versioned fields and objects.