REST Resource: monetization.subscriptions.basePlans

  • The subscriptions.basePlans resource does not have persistent data.

  • This resource provides methods to activate, deactivate, delete, and migrate prices for base plans.

  • Errors for operations on this resource include generic server errors (5xx) and concurrency update errors (409).

Resource

There is no persistent data associated with this resource.

Methods

activate

 Activates a base plan.

batchMigratePrices

 Batch variant of the MigrateBasePlanPrices endpoint.

batchUpdateStates

 Activates or deactivates base plans across one or multiple subscriptions.

deactivate

 Deactivates a base plan.

delete

 Deletes a base plan.

migratePrices

 Migrates subscribers from one or more legacy price cohorts to the current price.

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.