¶ How we handle API changes

The Ads API evolves over time as we add new features and improve existing functionality. We’re committed to giving you advance notice of any changes that might affect your applications.

¶ Our versioning approach

We follow semantic versioning principles and maintain backward compatibility whenever possible. When we do need to make breaking changes, we provide a 180-day transition period to give you time to update your integration.

¶ What constitutes a breaking change

Breaking changes are modifications that require you to update your code:

• Removing API endpoints or fields
• Changing data types or response formats
• Modifying authentication requirements
• Altering existing behavior in ways that could break your application

¶ When we make changes

For breaking changes, here’s what you can expect:

• 180 days advance notice through our developer communications
• Parallel support for both old and new versions during the transition
• Clear migration guidance with examples and best practices

Non-breaking changes like new optional fields, additional endpoints, or performance improvements may be released at any time without advance notice.