SCOPABLE API
Scopable REST API
Scopable has a full REST API (OpenAPI 3.1 at https://api.scopable.io/v1/openapi.json) covering 36 areas of the product, including clients, contacts, sites, opportunities, quotes, products, tickets, projects, agreements, compliance, assessments, QBRs, Microsoft 365 and Azure. Workspace admins create API keys under Settings → Developer with <domain>:read and <domain>:write scopes. API access is enabled per workspace on request. Scopable also runs a remote MCP server with OAuth.
What a key can call
The OpenAPI document lists 36 areas. A key sends Authorization: Bearer with an sk_live_ or sk_test_ key, and only the <domain>:read or <domain>:write scopes you grant.
API keys can read tickets, projects, products, org, team members, and permission groups. Those areas are not writable with an API key. Admin operations are refused to keys.
Lists use a cursor (limit 1 to 200, default 50). Writes require an Idempotency-Key of at most 255 characters.
Turn it on
- Ask Scopable to enable API access for the workspace.
- A workspace admin opens Settings, then Developer, and creates a key.
- Copy the key when it is shown. It is not shown again.
- Call
https://api.scopable.io/v1/.... A first read isGET /v1/clients?limit=1.
Assistants that should sign in as a user, instead of holding a key, use the MCP server.
36 areas
- Agreements
- Assessments
- Azure
- Clients
- Compliance
- Configurations
- ConnectWise inventory
- Contacts
- Dashboards
- Distributor catalog
- Presentation exports
- Deck download links
- Licenses
- Site deletion
- Microsoft 365
- Meetings
- Agent memory
- Opportunities
- Opportunity notes
- Organization
- Permission groups
- Products
- Projects
- PSA write-back
- QBR publications
- QBR templates
- QBR working documents
- Quotes
- Quote branding
- Security posture
- Service health
- Sites
- Source facets
- Team members
- Tickets