Stay organized with collections
Save and categorize content based on your preferences.
AI-generated Key Takeaways
This documentation outlines the process for using the AuthorizeSubscriptionAddon method to check with a reseller whether an add-on to a subscription is authorized.
The request is sent as a POST to a specific endpoint, replacing the domain name with the partner's domain.
The request body requires a unique requestId, details of the subscription, and details of the new line items being added.
The response includes an authorizationResult indicating the reseller's decision on the add-on request.
Required. The name of the subscription resource for which addon is being requested. It will have the format of "partners/{partner_id}/subscriptions/{subscriptionId}"
Request body
The request body contains data with the following structure:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-12 UTC."],[],["This describes an HTTP POST request to authorize an add-on for a subscription. The request, using gRPC Transcoding, targets a specific subscription identified by its `name` path parameter. The request body, in JSON format, includes a unique `requestId`, `subscription` details, and `newLineItems` for the add-on. The response, also in JSON, contains an `authorizationResult` field indicating whether the reseller approved the add-on request. The partner domain replaces the placeholder domain in the request URL.\n"]]