Identity compatibility
Identity compatibility
Follow the endpoint contract
Each public endpoint lists its accepted identities, credentials and scopes in API Reference. Historical endpoint tables do not establish current authorization requirements.
| Endpoint | Access requirements |
|---|---|
| GET /v1/users/me | USER; OAuth2 or API Key; user:profile |
| GET /v1/scopes | No credentials |
| POST /v1/creative/assets | USER or ORG; creative; remaining fields per API Reference |
Browser OAuth authorization uses accounts /oauth2/authorize; token exchange uses /oauth2/token. A protected business API RPC is not a browser sign-in entry point.
For authentication or permission failures, read the actual HTTP status and reason in error.details. Public REST errors use a nested error envelope. See errors and retries.