Canoe Intelligence OAuth Scopes

OAuth 2.0 searched

Canoe Intelligence 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.canoesoftware.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.

alternative-investmentsprivate-marketsdocument-automationdata-extractionfund-administrationcapital-callsk-1-tax-documentsportfolio-reportingfinancial-servicesfintechwealth-managementinstitutional-investors

Scopes: 0 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://api.canoesoftware.com/oauth/authorize

Token URL
https://api.canoesoftware.com/oauth/token https://api.canoesoftware.com/v1/tokens

Flows
authorizationCodeclientCredentials

Scopes (0)

Canoe Intelligence 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.

Canoe declares OAuth 2.0 authorizationCode and clientCredentials flows but publishes NO scopes — both flows carry an empty scopes map, no operation declares a scoped security requirement, and the documentation contains no scopes or permissions reference. An access token grants "access to all other endpoints within the API"; what a caller can actually reach is decided by the Canoe services their tenant purchased and by per-user permissions, and is signalled at call time with HTTP 403. This is an accurate zero, not a harvest miss.

📄 Provider scope reference: https://api.canoesoftware.com/docs

Source

OAuth Scopes

generated: '2026-08-09'
method: searched
source:
- openapi/canoe-intelligence-api-openapi.yml
- https://api.canoesoftware.com/docs
schemes:
- name: oauth2
  source: openapi/canoe-intelligence-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.canoesoftware.com/oauth/authorize
    tokenUrl: https://api.canoesoftware.com/oauth/token
  - flow: clientCredentials
    tokenUrl: https://api.canoesoftware.com/v1/tokens
  description: OAuth 2.0 authentication
scopes: []
docs: https://api.canoesoftware.com/docs
note: Canoe declares OAuth 2.0 authorizationCode and clientCredentials flows but publishes NO scopes — both flows
  carry an empty scopes map, no operation declares a scoped security requirement, and the documentation contains
  no scopes or permissions reference. An access token grants "access to all other endpoints within the API"; what
  a caller can actually reach is decided by the Canoe services their tenant purchased and by per-user permissions,
  and is signalled at call time with HTTP 403. This is an accurate zero, not a harvest miss.