The new Search Ads 360 Reporting API is now available. Join thesearchads-api-announcementsGoogle group to stay up to date on upcoming enhancements and releases.
There are major and minor versions, formatted asvMAJOR_MINOR. For example,v0_0is the
first major version, andv0_1the first minor version. The suffix of the
version number indicates the version type: for major versions it is always zero,
and for minor versions it is always greater than zero.
Major versions
Major releases introduce breaking changes, that is, changes that are not
backwards compatible.
Each major version has a separate endpoint, for example:
When upgrading from one major version to another, you may need to change your
code before switching to the new major version endpoint.
If you use aclient library,
you need to upgrade to the newest version. New major versions provide a
migration guide to help you fix any breaking changes in your code.
Examples of breaking changes include:
Removing or renaming a service, interface, field, method or enum value.
Changing the type of a field.
Changing a resource name format.
Changing the URL format in the HTTP definition.
Changing output formats, such as, changing0to--as the default value.
Changing the error reason returned from A to B.
Minor versions
Minor versions introduce only backwards-compatible changes.
When a minor version is released, the endpoint that is already in use is
automatically updated. This does not cause your code to break. You can continue
to use your existing client library.
Minor versions include new features or updates that do not affect your existing
code. If you want to use the new features, you need to upgrade yourclient libraryto the latest
version.
Sunsets
When an older Search Ads 360 Reporting API version is scheduled to sunset, we
post a notice on thesearchads-api-announcementsGoogle group.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eThe Search Ads 360 Reporting API uses semantic versioning with major and minor versions, where major versions introduce breaking changes and minor versions are backwards-compatible.\u003c/p\u003e\n"],["\u003cp\u003eMajor version releases require code changes and utilize separate endpoints, while minor version releases automatically update the existing endpoint without breaking existing code.\u003c/p\u003e\n"],["\u003cp\u003eBreaking changes in major versions might involve removing or renaming elements, changing types or formats, or modifying outputs and error reasons.\u003c/p\u003e\n"],["\u003cp\u003eMinor versions bring new features or updates but do not affect existing code; to utilize new features, upgrade your client library.\u003c/p\u003e\n"],["\u003cp\u003eSunset notices for older API versions are posted on the searchads-api-announcements Google group.\u003c/p\u003e\n"]]],["The Search Ads 360 Reporting API uses semantic versioning with major (e.g., v0) and minor (e.g., v0_1) versions. Major versions have breaking changes, require code modifications, a new endpoint, and client library upgrades. Minor versions are backward-compatible, automatically update the existing endpoint, and only require client library upgrades for new features. Breaking changes may involve removing or renaming elements, changing field types or output formats. Sunsets are posted on the Google group.\n"],null,["# Versioning in the Search Ads 360 Reporting API\n\nThe Search Ads 360 Reporting API uses [semantic versioning](https://semver.org/).\n\nThere are major and minor versions, formatted as\n`v`\u003cvar translate=\"no\"\u003eMAJOR\u003c/var\u003e`_`\u003cvar translate=\"no\"\u003eMINOR\u003c/var\u003e. For example, `v0_0` is the\nfirst major version, and `v0_1` the first minor version. The suffix of the\nversion number indicates the version type: for major versions it is always zero,\nand for minor versions it is always greater than zero.\n\nMajor versions\n--------------\n\nMajor releases introduce breaking changes, that is, changes that are not\nbackwards compatible.\n\nEach major version has a separate endpoint, for example: \n\n```text\nhttps://searchads360.googleapis.com/v0\n\nhttps://searchads360.googleapis.com/v1\n```\n\nWhen upgrading from one major version to another, you may need to change your\ncode before switching to the new major version endpoint.\n\nIf you use a [client library](/search-ads/reporting/client-libraries/client-libraries),\nyou need to upgrade to the newest version. New major versions provide a\nmigration guide to help you fix any breaking changes in your code.\n\nExamples of breaking changes include:\n\n- Removing or renaming a service, interface, field, method or enum value.\n- Changing the type of a field.\n- Changing a resource name format.\n- Changing the URL format in the HTTP definition.\n- Changing output formats, such as, changing `0` to `--` as the default value.\n- Changing the error reason returned from A to B.\n\nMinor versions\n--------------\n\nMinor versions introduce only backwards-compatible changes.\n\nWhen a minor version is released, the endpoint that is already in use is\nautomatically updated. This does not cause your code to break. You can continue\nto use your existing client library.\n\nMinor versions include new features or updates that do not affect your existing\ncode. If you want to use the new features, you need to upgrade your\n[client library](/search-ads/reporting/client-libraries/client-libraries) to the latest\nversion.\n\nSunsets\n-------\n\nWhen an older Search Ads 360 Reporting API version is scheduled to sunset, we\npost a notice on the [searchads-api-announcements](https://groups.google.com/g/searchads-api-announcements) Google group."]]
