API Clients Domains and Scopes

How Amerencio API client configuration works.

Clients, Domains, and Scopes

Amerencio API access is built around clients, domains, and scopes.

Docs screenshot placeholder

Screenshot target: API client settings showing client ID, allowed domains, scopes, and approval status. #22

Clients

A client represents an application, website, or integration. It has credentials, settings, and allowed domains.

Domains

Domains tell Amerencio where the client is allowed to operate. API requests include client headers and domain context so Amerencio can enforce the correct access rules.

Scopes

Scopes define what a client may access. Examples include profile information, addresses, payment-related data, or other user-specific resources.

Users approve access before a client can use protected scopes.

Review checklist

Client is active.
Domain is verified and active.
Client secret is not exposed in frontend code.
Required scopes are enabled.
User has approved the required scope.
Test/live mode matches the request context.