Google Play Developer Publishing API의 Edits 메서드를 사용하면 Google Play 앱의 여러 가지 변경사항을 준비한 다음 한 번에 배포할 수 있습니다. 이렇게 하려면 앱에 적용할 모든 변경사항이 포함된 edit을 만듭니다. Edit에는 다음과 같은 정보가 포함됩니다.
앱과 연결된 APK 및 각 APK의 '트랙'
각 APK는 '트랙'과 연결되어 있으며 트랙은 APK를 볼 수 있는 사용자를 결정합니다. 이렇게 하면 테스터에게 알파 및 베타 버전의 앱을 제공할 수 있습니다. 또한 앱의 한정 출시인 '단계적 출시' 버전을 제공할 수 있습니다. 이 앱은 개발자가 설정한 출시 비율에 따라 제한된 수의 앱 사용자에게 자동으로 제공되며, 이를 이용하여 점진적으로 앱의 새 프로덕션 버전을 배포할 수 있습니다.
앱의 Google Play 스토어 등록정보 언어별 버전
스토어 등록정보의 언어별 버전에는 스크린샷 및 기타 프로모션 그래픽, 현지화된 설명 등이 포함될 수 있습니다.
처음 edit을 만들면 생성된 edit은 앱의 현재 배포 상태의 사본입니다. 그다음, Edits 메서드를 호출하여 edit을 수정할 수 있습니다. edit이 준비되면 커밋하여 변경사항을 적용합니다. 언제든지 edit을 사용하지 않고 변경사항을 삭제하여 앱을 그대로 유지할 수도 있습니다.
이 API는 기존 앱(최소 하나의 APK가 업로드되어 있음)에 변경사항을 적용할 때만 사용할 수 있습니다. 따라서 이 API를 사용하려면 먼저 Play Console을 통해 하나 이상의 APK를 업로드해야 합니다. 또한 이 API를 사용하여 앱의 상태를 'published'에서 'unpublished'로 변경하거나 게시에 필요한 법적 동의를 작성하면 안 됩니다. 앱을 게시하려면 Play Console을 사용해야 합니다.
워크플로
이 섹션에서는 Google Play Developer Publishing API Edits 메서드를 사용하여 앱을 수정하는 일반적인 방법을 보여줍니다.
[null,null,["최종 업데이트: 2025-08-04(UTC)"],[[["\u003cp\u003eThe Google Play Developer Publishing API allows you to make changes to your app, such as updating APKs, store listings, and expansion files, using the "edits" functionality where you prepare changes in an edit and deploy them all at once by committing the edit.\u003c/p\u003e\n"],["\u003cp\u003eEdits enable managing APKs and their tracks (alpha, beta, staged rollout, production) allowing for controlled releases to testers and users.\u003c/p\u003e\n"],["\u003cp\u003eStore listings can be localized with language-specific descriptions, screenshots, and promotional graphics using edits.\u003c/p\u003e\n"],["\u003cp\u003eWhen an edit is committed, changes go live and can take several hours to fully propagate, but before that, edits can be modified further or discarded without affecting the live app.\u003c/p\u003e\n"],["\u003cp\u003eEdits functionality does not cover in-app products, standard products, subscriptions, unpublishing apps, or managing legal consents, which require separate API calls or the Play Console.\u003c/p\u003e\n"]]],["The Google Play Developer Publishing API uses \"edits\" to manage app changes. You create an edit, which initially mirrors the live app, and then modify it by uploading APKs, assigning them to tracks (alpha, beta, staged rollout), and updating localized store listings. These changes are made to the edit, not the live app. Finally, you commit the edit to make the changes live or abandon the edit to discard them. Only one edit per app can be active and changes through the Play Console discard any existing edits.\n"],null,["# Edits\n\nThe Google Play Developer Publishing API [Edits methods](/android-publisher/api-ref/rest/v3/edits#METHODS_SUMMARY)\nallow you to prepare a number of\nchanges to your Google Play app, then deploy them all at once. You do\nthis by creating an **edit**, which holds all the changes you want to\nmake to the app. The edit holds such information as:\n\n- Which APKs are associated with the app, and a \"track\" for each APK.\n\n Each is associated with a \"track\", determining which users see\n it. This allows you to provide alpha and beta versions of the app\n for your testers. In addition, you can provide a limited-release\n \"staged rollout\" version of the app; this app is automatically\n served to a limited number of the app's users (determined by the\n rollout percentage you set), allowing you to deploy a new\n production version of the app gradually.\n- Language and locale-specific versions of the app's Google Play\n Store listing\n\n Each locale-specific version of the store listing can contain\n screenshots and other promotional graphics, localized descriptive\n text, and so on.\n\n| **Note:** Not all the methods provided by the Google Play Developer API use the new, transactional \"edits\" functionality. Methods for the [inappproducts](/android-publisher/api-ref/rest/v3/inappproducts), [products](/android-publisher/api-ref/rest/v3/purchases.products), and [subscriptions](/android-publisher/api-ref/rest/v3/purchases.subscriptions) resources take effect immediately, whether or not there is an open edit for the app. Each resource's API reference page notes specifically whether the methods for that resource use the \"edits\" model.\n\nWhen you first create an edit, the edit is a copy of the current\ndeployed state of the app. You can then modify the edit by calling the\nEdits methods. When the edit is ready to go, you commit it,\nmaking the changes live. You can also abandon the edit at any time,\ndiscarding the changes and leaving your app as it was.\n\nYou can only use this API to make changes to an *existing* app (that\nhas at least one APK uploaded); thus, you will have to upload at least\none APK through the Play Console before you can use this\nAPI. Furthermore, you cannot use this API to change an app's state\nfrom \"published\" to \"unpublished\", or to fill out the legal consents\nrequired for publishing. To publish the app, you have to use the\nPlay Console.\n| **Caution:** If anyone makes any changes to the app through the Google Play Console while you have an edit in progress, your edit is discarded and the Play Console changes take effect.\n\nWorkflow\n--------\n\nThis section shows the typical way you would use the Google Play Developer Publishing API\n[Edits methods](/android-publisher/api-ref/rest/v3/edits#METHODS_SUMMARY) to make modifications to an app.\n\n1. Create a new edit, by calling [Edits:\n Insert](/android-publisher/api-ref/rest/v3/edits/insert) and specifying the app you want\n to modify.\n\n This creates a new edit of the specified app. The app's initial\n settings--the APKs, store listings, expansion files, and so on--are all\n copied from the deployed version of the app.\n2. Modify the edit as desired.\n\n You can make most of the changes which could be made through the\n Google Play Console. You do this by calling the\n appropriate Google Play Developer API method, and passing the IDs of the app\n and edit you want to modify. Specifically:\n - You can upload new APKs by calling [Edits.apks:\n upload](/android-publisher/api-ref/rest/v3/edits.apks/upload). This puts the APK in a storage area, so it can be assigned to a track in this or a subsequent edit.\n - You can assign APKs to tracks by calling [Edits.tracks:\n update](/android-publisher/api-ref/rest/v3/edits.tracks/update). You can also change the track assignments for existing APKs by calling [Edits.tracks:\n patch](/android-publisher/api-ref/rest/v3/edits.tracks/patch).\n - You can create a new localized store listing by calling [Edits.listings:\n update](/android-publisher/api-ref/rest/v3/edits.listings/update). You can modify an existing store listing by calling [Edits.listings: patch](/android-publisher/api-ref/rest/v3/edits.listings/patch).\n - You can add or modify expansion files by calling the [Edits.expansionfiles resource](/android-publisher/api-ref/rest/v3/edits.expansionfiles) methods.\n\n These methods make changes to the edit you have in progress, but\n they do *not* modify the live version of the app. You can make\n further changes or discard the edit in progress without affecting\n the user experience.\n | **Note:** Each user may have only a single edit open at a time. If you create a new edit, any existing edit you may have open is invalidated. In addition, if anyone commits an edit or makes changes to an app through the Play Console, *all* other edits for the app (owned by any user) are invalidated. If you try to commit an invalid edit, the operation will throw an exception and have no effect.\n3. Commit the edit.\n\n When you call [Edits: commit](/android-publisher/api-ref/rest/v3/edits/commit), if there\n are no validation errors, then all the changes specified in the\n edits resource go \"live\", replacing the current state of the\n app. These changes can take several hours to take effect, just as\n when you make changes through the Play Console."]]