Audit and Update a Subscription Product
A 4-step recipe with Android. We can help you get access.
Recipe · 4 steps
Audit and Update a Subscription Product
with Android · Plan & Entitlement Design
List the subscription catalog, read one product, patch it with a field mask, and confirm the result.
- List the application's subscription products to establish what the catalog looks like before any change is made.
- Read the target subscription's live configuration so the patch is applied against current state rather than a stale local copy.
- Patch the subscription, writing only the fields named in the update mask. Fields outside the mask are left exactly as they were.
- Read the subscription back to confirm the masked update persisted and nothing outside the mask was disturbed.
What you'll need to have ready
- packageName: The package name of the application (e.g. com.example.myapp).
- productId: The id of the subscription product to update.
- updateMask: FieldMask naming exactly which fields to update (e.g. listings). Only the named fields are written.
- subscriptionPatch: The Subscription body carrying the new values for the fields named in the update mask.
- showArchived: Whether the catalog listing should include archived subscriptions.
- pageSize: Maximum number of subscriptions to return in the audit listing.
- latencyTolerance: Propagation latency tolerance: PRODUCT_UPDATE_LATENCY_TOLERANCE_LATENCY_SENSITIVE or PRODUCT_UPDATE_LATENCY_TOLERANCE_LATENCY_TOLERANT.
- regionsVersion: The version of the available regions being used for pricing.
For your developer
Arazzo workflow android:audit-update-subscription, 4 operations: listSubscriptions → getSubscription → updateSubscription → getSubscription. Specs on APIs.io.