Moody's · OAuth Scopes
Moody's OAuth Scopes
OAuth 2.0
derived
Moody’s 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.economy.com/data/v1/oauth2/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.
Climate RiskComplianceCredit RiskEconomic DataEntity VerificationFinancial AnalyticsInsuranceKYCRiskScreening
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api.economy.com/data/v1/oauth2/token
https://api.economy.com/data/v1/oauth2/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Moody's 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.
Moody's APIs do not use OAuth scopes — the Data Buffet API user guide (https://github.com/moodysanalytics/databuffet-api-codesamples/blob/master/dataBuffet-api-userguide.md) documents an OAuth2 client_credentials flow with access/encryption keys and no scope parameter, and permissions across Moody's products are tied to account entitlements and roles rather than scopes.
Moody's APIs do not use OAuth scopes — the Data Buffet API user guide (https://github.com/moodysanalytics/databuffet-api-codesamples/blob/master/dataBuffet-api-userguide.md) documents an OAuth2 client_credentials flow with access/encryption keys and no scope parameter, and permissions across Moody's products are tied to account entitlements and roles rather than scopes.
📄 Provider scope reference: https://github.com/moodysanalytics/databuffet-api-codesamples/blob/master/dataBuffet-api-userguide.md