Cledara · OAuth Scopes
Cledara OAuth Scopes
OAuth 2.0
probed
Cledara publishes 1 OAuth 2.0 scope via the authorization_code and client_credentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Cledara API on a user’s behalf.
Tokens are issued from https://data.cledara.com/oauth/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.
FinanceSaaS ManagementSoftware SpendingSpend ManagementSubscription ManagementVirtual CardsExpense ManagementFinOpsMCPMarket Data
Scopes: 1
Flows: authorization_code, client_credentials
Method: probed
OAuth endpoints
Authorization URL
https://data.cledara.com/authorize
https://data.cledara.com/authorize
Token URL
https://data.cledara.com/oauth/token
https://data.cledara.com/oauth/token
Flows
authorization_codeclient_credentials
authorization_codeclient_credentials
Scopes (1)
| Scope | Description | Flows |
|---|---|---|
| mcp:read | Read access to the Cledara SaaS Market Data Hub through the MCP endpoint at https://data.cledara.com/mcp. Declared in scopes_supported of the RFC 8414 authorization-server metadata; Cledara publishes no prose scope reference, so the description here is derived from the scope name plus the endpoint it guards. |
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.