このガイドでは、Merchant API でのバージョニング、リリース、さまざまなバージョンのライフサイクルの処理方法について説明します。
バージョニング体系
Merchant API では、サブ API レベルでバージョニング戦略が採用されています。つまり、Merchant API 内の Products など、各 API には独自のバージョン ライフサイクルがあります。
バージョン管理の形式とプレゼンテーション
安定版のサブ API バージョン: サブ API が安定版の場合、そのすべてのメソッドは安定版です。安定版のサブ API バージョンは vX（v1、v2 など）として表されます。これらは本番環境で使用できるメジャー バージョンです。
アルファ版のサブ API バージョン: サブ API がアルファ版の場合、そのすべてのメソッドはアルファ版です。アルファ版のサブ API バージョンは vXalpha（v1alpha、v2alpha など）として表されます。これらには、テストと迅速な反復を目的とした試験運用版の早期アクセス機能が含まれています。アルファ版には安定性の保証がなく、ライフサイクルも定義されていません。30 日間の通知期間で変更または廃止される可能性があります。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-03 UTC。"],[],[],null,["This guide explains how Merchant API handles versioning, releases, and the\nlifecycle of its different versions.\n\nVersioning scheme\n\nMerchant API employs a versioning strategy at the sub-API level. This means that\neach API, for example Products within the Merchant API, will have its own\nversion lifecycle.\n\nVersioning format and presentation\n\n- **Stable sub-API versions:** If a sub-API is in a stable version then all\n its methods are in a stable version. A stable sub-API version is represented\n as **vX** (for example, **v1** , **v2**). These are production-ready major\n versions.\n\n- **Alpha sub-API versions:** If a sub-API is in an alpha, then all its\n methods are in alpha. An alpha sub-API version is represented as\n **vXalpha** (for example, **v1alpha** , **v2alpha**). They contain\n experimental, early access features intended for testing and rapid\n iteration. Alpha versions come with no stability assurance, have no defined\n lifespan and can be changed or discontinued with a notice period of 30 days.\n\nVersion changes\n\n- **Major version increments** (for example, v1 to v2): These signal\n backward-incompatible and breaking changes, which require developer action.\n Only breaking changes of stable sub-APIs will have a new version number. For\n example, v1 to v2.\n\n- **Minor changes:** Backward compatible additions or fixes are presented as\n changes to the existing major version. Such changes will be detailed in the\n release notes for that major version. Non-breaking additions to a sub-API\n will be released to the alpha channel of the latest stable version or\n directly to the latest stable version.\n\nSunset policy\n\nWe periodically sunset older Merchant sub-API versions. We commit to a 12-month\ndeprecation window for stable major versions (vX), starting from the official\ndeprecation announcement.\n\nFor example, if we deprecate v1 of the Products sub-API on January 15, 2026, it\nwill sunset no earlier than January 15, 2027. Beyond this date, the earlier\nversion of the sub-API will no longer be available for use.\n\nSub-API version and lifecycle status\n\nThe following table lists the latest versions of each sub-API of Merchant API:\n\n| Sub-API | Versions | Status |\n|-------------------------|----------------|-------------------------------------------|\n| Accounts | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Conversions | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Data sources | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Inventories | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Issue resolution | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Local feeds partnership | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Notifications | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Order tracking | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Products | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Product Studio | v1alpha | Active |\n| Promotions | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Quota | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Reports | v1 v1beta | Active To be discontinued on Feb 28, 2026 |\n| Reviews | v1alpha v1beta | Active To be discontinued on Feb 28, 2026 |\n\nBest practices\n\n- Regularly check the release notes and [latest\n updates](/merchant/api/latest-updates) for new versions, major updates, improvements, and announcements about sub-API launches and deprecations.\n- If a sub-API has two or more stable versions, we suggest using the latest version at all times.\n- Design your application to gracefully handle various sub-API errors, including network issues, rate limits, and the new error codes or messages that might be introduced with newer sub-API versions.\n- Don't wait until a sub-API version is about to be sunset to start planning your upgrade. Begin evaluating and testing new versions as soon as they are available.\n- For feature requests or concerns about a sub-API roadmap, [reach out to us\n with questions or feedback](/merchant/api/support/give-feedback). For information about how to contact the Merchant API team for technical support, see [Get help with Merchant API](/merchant/api/support/get-help)."]]
