Cogny · OAuth Scopes

Cogny OAuth Scopes

OAuth 2.0 searched

Cogny publishes 8 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Cogny API on a user’s behalf.

Tokens are issued from https://cogny.com/api/mcp/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.

CompanyAi Enterprise SoftwareMarketingMarketing AnalyticsMarketing AutomationMCPAgentsData WarehouseAdvertising

Scopes: 8 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://cogny.com/api/mcp/oauth/authorize

Token URL
https://cogny.com/api/mcp/oauth/token

Flows
authorizationCode

Scopes (8)

Scope	Description	Flows
read	Read access
write	Write access
tickets:read	Read tickets
tickets:write	Write tickets
reports:read	Read growth reports
reports:write	Create/cancel growth reports
warehouses:read	Read connected warehouses
warehouses:write	Manage connected warehouses

📄 Provider scope reference: https://cogny.com/docs/api-overview-authentication

Source

OAuth Scopes

generated: '2026-07-18'
method: searched
source: openapi/cogny-openapi.yml
docs: https://cogny.com/docs/api-overview-authentication
schemes:
  - name: oauth2
    source: well-known/cogny-oauth-authorization-server.json
    flows:
      - flow: authorizationCode
        authorizationUrl: https://cogny.com/api/mcp/oauth/authorize
        tokenUrl: https://cogny.com/api/mcp/oauth/token
    description: OAuth 2.1 (DCR + PKCE) for MCP clients.
scopes:
  # From the OAuth authorization-server metadata (MCP surface)
  - {scope: read, description: Read access, source: well-known}
  - {scope: write, description: Write access, source: well-known}
  - {scope: 'tickets:read', description: Read tickets, source: well-known}
  - {scope: 'tickets:write', description: Write tickets, source: well-known}
  # From the REST API key-scope reference (docs)
  - {scope: 'reports:read', description: Read growth reports, source: docs}
  - {scope: 'reports:write', description: Create/cancel growth reports, source: docs}
  - {scope: 'warehouses:read', description: Read connected warehouses, source: docs}
  - {scope: 'warehouses:write', description: Manage connected warehouses, source: docs}
notes: >-
  Two scope surfaces: the OAuth MCP flow advertises read/write/tickets:*; the REST
  API-key generator (Settings > API Keys) offers reports:*, tickets:read, warehouses:*.