Fannie Mae · OAuth Scopes
Fannie Mae OAuth Scopes
OAuth 2.0
probed
Fannie Mae 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.
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.
Federal-GovernmentHousingMortgagesFinanceGSEFortune 100
Scopes: 0
Flows:
Method: probed
Scopes (0)
Fannie Mae 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.
These are the scopes Fannie Mae's own OAuth 2.0 / OpenID Connect authorization server advertises, read from its published discovery document. Fannie Mae does NOT publish a scope reference page, and no public OpenAPI declares per-operation security requirements, so the mapping of scope to API operation is not public. Descriptions below marked `inferred: true` are our reading of the scope name, not a Fannie Mae definition — nothing here is quoted from a Fannie Mae scopes document, because no such document is published.
These are the scopes Fannie Mae's own OAuth 2.0 / OpenID Connect authorization server advertises, read from its published discovery document. Fannie Mae does NOT publish a scope reference page, and no public OpenAPI declares per-operation security requirements, so the mapping of scope to API operation is not public. Descriptions below marked `inferred: true` are our reading of the scope name, not a Fannie Mae definition — nothing here is quoted from a Fannie Mae scopes document, because no such document is published.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.