AT&T Developer Hub · OAuth Scopes
AT&T Developer Hub OAuth Scopes
OAuth 2.0
derived
AT&T Developer Hub uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
Tokens are issued from https://api.att.com/oauth/v4/token.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
Fortune 1005GNetwork APIsCAMARAConnectivityTelecommunicationsEdge ComputingDevice StatusSIM Swap
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api.att.com/oauth/v4/token
https://api.att.com/oauth/v4/token
Flows
clientCredentials
clientCredentials
Scopes (0)
AT&T Developer Hub implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
AT&T publishes no OAuth scopes for the Developer Hub's invite-only CAMARA network APIs, which use a client_credentials flow (https://devex-web.att.com/developer-hub/docs/network-api-accelerator-program); the OAuth 2.0 scope documentation at https://developer.att.com/oauth-2/docs covers only legacy APIs (SMS, MMS, ADS, Speech).
AT&T publishes no OAuth scopes for the Developer Hub's invite-only CAMARA network APIs, which use a client_credentials flow (https://devex-web.att.com/developer-hub/docs/network-api-accelerator-program); the OAuth 2.0 scope documentation at https://developer.att.com/oauth-2/docs covers only legacy APIs (SMS, MMS, ADS, Speech).
📄 Provider scope reference: https://developer.att.com/oauth-2/docs