Google Play Console には、REST ベースのウェブサービス API のスイートが用意されています。これらの API を使用して、アプリに対し公開、レポート作成などのアプリ管理機能を直接実行できます。
すべてのデベロッパーがこれらのデベロッパー向け API を使用する必要があるわけではありません。ほとんどの場合は、Google Play Console を使用して引き続きアプリを直接管理できます。ただし、管理する APK の数が多い場合や、ユーザーの購入や定期購入を管理する必要がある場合は、これらの API を使用すると便利です。
含まれる内容
新規市場にビジネスを拡大する際も、Google Play Developer API を利用すればリリース管理に割く時間と手間を削減し、アプリの設計と開発に集中できます。
Google Play Console には、アプリの管理に役立つ API のスイートが用意されています。
Publishing API を使用すると、アプリのアップロード、公開、およびその他の公開関連のタスクを実行できます。
定期購入が期限切れになるか更新されると RTDN が届くため、有効期限に基づいて API 呼び出しのスケジュールを設定する必要はありません。
Reporting API
Reporting API は、Google Play Console のデータに基づいた自動化ワークフローの作成を希望するデベロッパーや、他のデータセット以外に、Google Play Console のデータを内部のビジネス レポートや分析に使う可能性があるデベロッパー向けの API です。この API を使用して、内部のレポート作成、分析、自動化に使用するアプリレベルのデータや指標にプログラムでアクセスできます。
Reporting API から、クラッシュ発生率、ANR 発生率、wake up と wake lock の問題、エラー スタック トレースなど、Android Vitals のデータにアクセスできます。
おすすめの方法
このバージョンの Reporting API の秒間クエリ数はデフォルトで 10 件に制限されています。クエリの使用は、Google Cloud コンソールの [割り当て] セクションで確認できます。この制限を超えるクエリが必要な場合は、こちらのフォームから割り当てリクエストを送信してください。
Reply to Reviews API
Reply to Reviews API を使用すると、アプリに対するユーザーのフィードバックを表示し、そのフィードバックに返信することができます。この API により、CRM システムなどの既存のカスタマー サポート ツールキット内でユーザーと直接やり取りできます。
Reply to Reviews API では、製品版のアプリに対するフィードバックにのみアクセスできます。アルファ版またはベータ版のアプリに対するフィードバックを表示するには、Google Play Console を使用してください。また、この API はコメントを含むレビューのみを表示します。ユーザーがアプリを評価したがコメントを入力しなかった場合、この API でそのフィードバックにアクセスすることはできません。
Permissions API
Permissions API を使用することで、デベロッパーは Google Play Console 内での権限の管理を自動化できます。これにより、手動で操作することなく、デベロッパー アカウントへのアクセス権を持つユーザーを柔軟に管理できます。
Permissions API では、次のような管理機能を実行できます。
ユーザーが退職した場合にアクセス権を削除する。
ユーザーが関連チームに加入した場合にアプリへのアクセス権を付与する。
Voided Purchases API
Voided Purchases API からは、ユーザーが取り消した購入に関連付けられている注文のリストが提供されます。このリストの情報を基に、ユーザーがそれらの注文からアイテムにアクセスできないようにする取り消しシステムを実装できます。
この API の対象は、1 回限りのアプリ内注文とアプリ定期購入です。
購入は以下の方法で取り消すことができます。
ユーザーが注文に対する払い戻しをリクエストする
ユーザーが注文をキャンセルする
注文のチャージバックが行われる
デベロッパーが注文のキャンセルまたは払い戻しを行う（注: Voided Purchases API には取り消し済みの注文のみが表示されます。そのため、デベロッパーが取り消しオプションを設定せずに払い戻しを行った注文は、この API に表示されません）
Google が注文のキャンセルまたは払い戻しを行う
この API を使用すると、特にアプリがゲームの場合、アプリのすべてのユーザーに対してより公平なエクスペリエンスを提供できます。
[[["わかりやすい","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-07-27 UTC。"],[],[],null,["# Google Play Developer APIs\n\nOverview\n--------\n\nThe Google Play Console provides a suite of REST-based web service APIs that let\nyou perform publishing, reporting, and other app-management functions directly\nfor your app.\n\nNot all developers need to use these developer APIs --- in most cases you can\ncontinue to manage your apps directly using the Google Play Console. However,\nif you have a large number of APKs to manage, or have to track user purchases\nand subscriptions, you might find these APIs to be useful.\n\n### What's included\n\nThe Google Play Developer APIs let you focus on designing and developing your\napp, while spending less time and effort managing your releases, even as you\ngrow to new markets.\n\nThe Google Play Console includes a suite of APIs that you can use to manage your\napp:\n\n- The [Publishing API](#publishing) lets you upload and publish apps, and perform other publishing-related tasks.\n- The [Subscriptions and In-App Purchases API](#subscriptions) lets you manage in-app purchases and subscriptions. (This was previously known as the \"Purchase Status API\".)\n- The [Reporting API](#reporting) lets you retrieve information about your app's quality from Android vitals.\n- The [Reply to Reviews API](#reviews) lets you retrieve and reply to reviews of your app.\n- The [Permissions API](#permissions) lets you automate permission management within the Play Console.\n- The [Play Games Services Management API](/games/pgs/management/management) lets you issue REST calls to programmatically control the metadata underlying the Google Play Games Services features.\n- The [Voided Purchases API](#voided-purchases) provides a list of orders that are associated with purchases that a user has voided.\n\n### Getting started\n\nTo get started with the Google Play Developer APIs, see the [getting\nstarted](https://developers.google.com/android-publisher/getting_started)\ndocumentation.\n\nPublishing API\n--------------\n\nThe [Publishing API](https://developers.google.com/android-publisher#publishing)\nlets you to automate frequent tasks having to do with app distribution.\nThis provides functions similar to those available to a developer through the\nPlay Console, such as:\n\n- Uploading new versions of an app\n- Releasing apps, by assigning APKs to various [tracks](https://developers.google.com/android-publisher/tracks) (alpha, beta, staged rollout, or production)\n- Creating and modifying Google Play Store listings, including localized text and graphics and multidevice screenshots\n\nThose tasks are performed using the\n[edits](https://developers.google.com/android-publisher/edits)\nfunctionality, which takes a transactional approach to making changes.\nThis lets you bundle several changes into a single draft edit, then commit\nthe changes all at once. (None of the changes take effect until the edit is\ncommitted.)\n| **Note:** Not all developers need to use this API. All the functionality provided by the API is also available through the Google Play Console. However, this API lets you integrate your app and listing update process with your existing tools, which is useful for some developers. In particular, if you have a large number of APKs to manage, or localized listings in many different locales, you may find this API invaluable.\n\n### Best practices\n\n- Limit the number of app updates. Don't publish alpha or beta updates more frequently than once a day (production apps should be updated even less frequently than that). Every update costs your users time and possibly money. If you update too frequently, users might start ignoring updates, or even uninstall the product.\n\nSubscriptions and In-App Purchases API\n--------------------------------------\n\nThe [Subscriptions and In-App Purchases API](https://developers.google.com/android-publisher#subscriptions)\nallows you to manage your app's\ncatalog of in-app products and subscriptions. In addition, with the\nSubscriptions and In-App Purchases API, you can quickly retrieve the details of\nany purchase using a standard `GET` request.\n\nIn the request, you supply information about the purchase --- app package name,\npurchase or subscription ID, and the purchase token. The server responds with a\nJSON object describing the associated purchase details, order status, developer\npayload, and other information.\n\nYou can use this API in several ways, such as for reporting and\nreconciliation of individual orders and for verifying purchases and subscription\nexpirations. You can also use the API to learn about canceled orders and confirm\nwhether in-app products have been consumed, including whether they were consumed\nbefore being canceled.\n| **Note:** The Subscriptions and In-App Purchases API does not use the transactional \"edits\" functionality used by the [Publishing API](/google/play/developer-api/publisher-api). Methods for the [Inappproducts](https://developers.google.com/android-publisher/api-ref/rest/v3/inappproducts) and [Purchases.subscriptions](https://developers.google.com/android-publisher/api-ref/rest/v3/purchases.subscriptions) resources take effect immediately. Each resource's API reference page notes specifically whether the methods for that resource use the \"edits\" model.\n\n### Best practices\n\n- Store subscription information on your server to avoid making unnecessary API calls. When your app needs to verify a subscription, you should rely on the cached information on your server instead of repeating the API call to Google.\n- There are two scenarios in which your secure server should use the Google Play Developer API to get subscription information:\n - Your server receives a new purchase token that has not been seen before.\n - Your server receives a real-time developer notification (RTDN), which indicates that you need to use the purchase token to get the new subscription information.\n- Don't poll the API for subscription status on a regular basis. For example, don't call the API daily to check each subscription.\n- Since you receive an RTDN when the subscription expires or renews, you don't need to schedule an API call based on the scheduled expiry time.\n\nReporting API\n-------------\n\nThe [Reporting API](https://developers.google.com/play/developer/reporting)\nis for developers who want to build automated workflows on top of\nPlay Console data, or developers who use Play Console data for internal business\nreporting and analysis, potentially alongside\nother datasets. This gives you programmatic access to app-level data and metrics\nfor internal reporting, analysis, and automation.\n\nThe reporting API offers access to Android vitals data,\nincluding crash rate, ANR rate, wake-up and wake-lock issues, and error stack\ntraces.\n\n### Best practices\n\n- This version of the Reporting API has a default limit of 10 queries per second. You can view your quota usage in the [Quotas section](https://pantheon.corp.google.com/apis/api/playdeveloperreporting.googleapis.com/quotas) of the Google Cloud Console. If you need to exceed this limit, you can submit a quota request using [this form](https://support.google.com/googleplay/android-developer/contact/apiqr).\n\nReply to Reviews API\n--------------------\n\nThe [Reply to Reviews API](https://developers.google.com/android-publisher/reply-to-reviews) allows you to view user feedback\nfor your app and reply to this feedback. You can use this API to interact with\nusers directly within your existing customer support toolkit, such as a CRM system.\n\nThe Reply to Reviews API allows you to access feedback only for production\nversions of your app. If you want to see feedback on alpha or beta versions of\nyour app, use the Google Play Console instead. Also, note that the API shows only\nthe reviews that include comments. If a user rates your app but does not provide\na comment, their feedback is not accessible from the API.\n\nPermissions API\n---------------\n\nThe Permissions API gives developers the ability to [automate permission\nmanagement](https://developers.google.com/android-publisher/api-ref/rest/v3/users/list)\nwithin the Play Console. This can allow you flexible control over who\nhas access to your developer account, without manual involvement.\n\nWith the Permissions API, you can perform administrative functions such as:\n\n- Removing users' access when they leave your company.\n- Granting access to an app when a user joins the relevant team.\n\nVoided purchases API\n--------------------\n\nThe [Voided Purchases API](https://developers.google.com/android-publisher/voided-purchases)\nprovides a list of orders that are associated with purchases that a user has\nvoided. You can use information from this list to implement a revocation system\nthat prevents the user from accessing products from those orders.\n\nThis API applies to one-time in-app orders and app subscriptions.\n\nA purchase can be voided in the following ways:\n\n- The user requests a refund for their order.\n- The user cancels their order.\n- An order is charged back.\n- Developer cancels or refunds order. Note: only revoked orders will be shown in the Voided Purchases API. If developer refunds without setting the revoke option, orders will not show up in the API.\n- Google cancels or refunds order.\n\nBy using this API, you help create a more balanced and fair experience for all\nof your app's users, particularly if your app is a game."]]
