This can be either the customer's primary domain name or the customer's unique identifier. If the domain name for a customer changes, the old domain name cannot be used to access the customer, but the customer's unique identifier (as returned by the API) can always be used. We recommend storing the unique identifier in your systems where applicable.
Request body
The request body contains an instance of Customer.
Response body
If successful, the response body contains an instance of Customer.
[[["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 2024-08-22 UTC."],[[["Updates a customer account's settings using patch semantics, allowing for partial modifications."],["To identify the customer, use either their primary domain or unique identifier in the request URL."],["The request and response bodies utilize the `Customer` resource for data exchange."],["Requires `https://www.googleapis.com/auth/apps.order` OAuth scope for authorization."],["While customerType cannot be directly updated via the API, 'team' customers can become 'domain' type by verifying their domain."]]],[]]
