Developers
Build on the Scopable 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. Every workspace includes API access, on every plan. Scopable also runs a remote MCP server with OAuth.
When to use Scopable
Use the REST API for scripts and integrations. Use the MCP server when a person wants Claude, ChatGPT, Claude Code, or Cursor to call the same workspace after they sign in.
- Read and update records the key's scopes allow.
- Page with
nextCursorand retry writes with the sameIdempotency-Key. - Receive signed client and contact webhooks.
- Connect an assistant at
https://mcp.scopable.io/mcpto read and write records. Read and write is the default, and read only is an option at consent.
Tickets, projects, products, org, team members, and permission groups are read-only for API keys.
How an agent calls Scopable
- Read the OpenAPI document and the getting-started guide.
- Ask a workspace admin for a key from Settings, then Developer. Every workspace includes API access.
- Send the key as a bearer token to
/v1routes onapi.scopable.io. - Send an
Idempotency-Keyon every write. - Branch on
error.code, retainerror.requestId, and obey the rate-limit headers.
Scopable REST API
36 product areas, bearer API keys, and how to request workspace access.
Open resourceScopable MCP server
Connect Claude, ChatGPT, Claude Code, or Cursor at mcp.scopable.io/mcp.
Open resourceScopable OpenAPI 3.1 specification
Machine-readable paths, schemas, and error codes for the live API.
Open resourceScopable API getting-started guide
Create an API key, authenticate, paginate, and send idempotent writes.
Open resourceScopable MCP setup guide
Connect Claude, ChatGPT, Claude Code, or Cursor, then revoke access.
Open resourceScopable signed webhooks
HMAC-SHA256 client and contact events from Settings, Developer, Webhooks.
Open resourceAPI reliability and lifecycle
Rate limits
Responses report RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy. A 429 also returns Retry-After.
Typed errors
Every failure returns a machine-readable code, a type, a message, and a requestId that is also sent in X-Request-Id.
Versioning and deprecation
Breaking changes require a new major URL version. Scheduled retirements use Deprecation (RFC 9745), Sunset (RFC 8594), and a rel="deprecation" link to migration guidance. No v1 retirement is scheduled.