REST Resource: apprecovery

  • The app recovery resource has no persistent data associated with it.

  • There are methods available to add targeting, cancel, create, deploy, and list app recovery actions.

  • Common error codes for this resource include 5xx for generic server errors and 409 for concurrency update errors.

Resource

There is no persistent data associated with this resource.

Methods

addTargeting

 Incrementally update targeting for a recovery action.

cancel

 Cancel an already executing app recovery action.

create

 Create an app recovery action with recovery status as DRAFT.

deploy

 Deploy an already created app recovery action with recovery status DRAFT.

list

 List all app recovery action resources associated with a particular package name and app version.

Error codes

The operations of this resource, return the following HTTP error codes:

Error code Reason Description Resolution
400 invalidValue An invalid value was provided in the request. This is often returned for a malformed or invalid purchase token. Correct the invalid field value in the request body or parameters based on the API reference.
400 required A required field or parameter is missing from the request. Consult the API documentation to ensure all mandatory fields and parameters are included.
403 userInsufficientPermission The user does not have sufficient permission to perform the requested operation. Ensure the authenticated user has the necessary permissions in the Google Play Console. See Using a service account for more details.
404 notFound The requested resource could not be found. Verify the identifiers (e.g., purchase token, package name, product ID, subscription ID) are correct.
409 concurrentUpdate There was an attempt to update an object that is being updated concurrently. Retry the request with exponential backoff. Avoid simultaneous modifications to the same resource.
5xx Generic error Generic error in the Google Play server. Retry your request.

If the problem persists contact your Google Play account manager or submit a support request. Consider checking the Play Status Dashboard for any known outages.