Chili Piper OAuth Scopes

generated: '2026-08-09'
method: searched
source: https://help.chilipiper.com/hc/en-us/articles/35576029581971-Edge-API-References
docs: https://help.chilipiper.com/hc/en-us/articles/35576029581971-Edge-API-References
description: >-
  Chili Piper API access tokens are scoped in Command Center at issue time. Scope is a matrix: a
  permission verb is granted per API section, so a token can be limited to exactly the surface a
  script or agent needs. The published OpenAPI documents declare only the apiKeyAuth bearer scheme
  and carry no oauth2 scope maps, so the matrix below is transcribed from Chili Piper documentation
  rather than derived from a spec.
model: permission-matrix
issuance:
  ui_path: 'Command Center > Integrations > Credentials > API Access Tokens > Generate Token'
  admin_only: true
  note: >-
    Only users with the Admin role can generate API tokens. Workspace Managers cannot access the
    credentials page. The token value is shown once and cannot be retrieved later.
  management: 'Tokens list shows Last Access, Created Date and Created By; tokens can be viewed for permissions, removed and deleted. Deleting a token revokes its access immediately.'
permissions:
  - {verb: Ping, description: Health/reachability check only.}
  - {verb: Read, description: Read access to the granted sections.}
  - {verb: Modify, description: Create and update access to the granted sections.}
  - {verb: Remove, description: Delete access to the granted sections.}
sections:
  - {section: Health, description: Monitor the health of the application.}
  - {section: Tenant, description: Organization tenant metadata.}
  - {section: Rule, description: Create/update/delete and list routing rules.}
  - {section: Workspace, description: Read workspaces, add and remove users.}
  - {section: Team, description: Read teams, add and remove users.}
  - {section: Distribution, description: List, update, publish and delete distributions.}
  - {section: Availability, description: Available slots of assignees in round-robin meetings.}
  - {section: User, description: Read/find users, invite users, update licenses.}
  - {section: CRM, description: Activity, cancel and no-show by CRM event ID.}
  - {section: Meetings, description: Query, get, cancel, no-show, activity and CSV export.}
  - {section: Concierge, description: Routers, routing, scheduling and logs.}
  - {section: 'Scheduling Links', description: List, initialize and schedule across link types.}
  - {section: Handoff, description: Initialize a handoff flow and schedule from a handoff session.}
named_scopes_documented:
  - scope: Concierge.schedule
    description: >-
      Required to run a Concierge router from outside the UI via the Edge API.
    source: https://help.chilipiper.com/hc/en-us/articles/30935152032275-Using-Concierge-via-the-Edge-API
oauth:
  used_by: MCP server (https://fire.chilipiper.com/api/fire-edge/v1/org/mcp)
  flow: browser-based authorization, Admin on a paid account only
  dynamic_client_registration: 'Client ID and secret are left blank by the client; no registration step is documented.'
  protected_resource_metadata: well-known/chili-piper-oauth-protected-resource.json
  published_scope_list: none
  note: >-
    Chili Piper publishes no OAuth scope list for the MCP OAuth path. The documentation states the
    OAuth grant carries the signing-in Admin's org-wide permissions, and recommends the API-key path
    when a narrower permission scope than the Admin OAuth grant is needed.