Customer API · How-To
Creating a Customer API Application
Use Create Application to obtain credentials for a server-to-server integration.
What this does
Use Create Application to obtain credentials for a server-to-server integration.
Steps
- Select the intended group or location, then open Settings > API Access.
- Choose Create Application and enter a recognizable application name.
- Select available Module Access choices. Location context limits creation to that location; group context uses the group. Permitted operations, expiration and rate limit come from your API grant, not free-form fields in this dialog.
- If Reviews is selected and your grant permits it, review the separate reply-operations checkbox. This does not authorize Google Customer API publishing.
- Review and accept the current Customer API Terms, then choose Accept & Create Application.
- Securely save the Client ID and one-time Client Secret. Never paste secrets into Support or documentation screenshots.
Customer creation controls and inherited scope
The customer wizard has three steps: Application name, Module access, and Customer API Terms. Name must be nonblank. Select at least one available module; occupied modules show their overlapping-location conflict. Scope comes from the selected group/location, and operation permissions, expiration and rate limit are inherited from the API grant. The customer wizard does not expose the internal tool's scope list, location subset, expiration picker or rate-limit input. Backend authorization remains authoritative even if a module appears in the UI. Terms must load and match the current version before issuance.
Reviews reply opt-in and provider limits
Reviews reply operations are separate from module selection and appear only when the displayed grant includes reviews:reply:write. The checkbox initializes off when the page mounts; inspect its value when reopening the dialog because the current close/success handlers do not reset it. A reply grant does not bypass provider restrictions: Google Customer API content reads and publishing remain policy-gated. See Reviews Customer API and webhooks for the provider-neutral contract.
What happens next
Your change is available within the scope you selected.
Warnings
- The client secret is a credential. Never paste it into a support case or browser application.