DevelopersOverview

Developers

Technical documentation for building against CE Canvas. If you are setting CE Canvas up for your organisation rather than writing code, the Integrations pages are for you.

Partner API

A versioned HTTP API a partner system uses to add documents and boundaries with measures to CE Canvas projects, under a credential an organisation admin issues and can revoke.

Base URLs: https://app.cecanvas.com/api/v1 (production, Australia) and https://staging.cecanvas.com/api/v1 (staging — the test tenant).

AI assistants (MCP)

CE Canvas exposes a Model Context Protocol server so practitioners can drive their projects from Claude, ChatGPT or any MCP client, with access scoped to the signed-in person. Setup is described under AI Assistants (MCP). The MCP surface is for a person or an assistant acting on their behalf; the Partner API is for a system acting as itself.

Conventions shared across surfaces

  • Every response carries X-Request-Id; quote it when you contact us.
  • Errors use one envelope with a stable machine-readable type.
  • Access is always scoped by the credential or person making the request; nothing is service-wide.

Getting access

Email support@cecanvas.com. For the Partner API we set up a staging organisation whose admin issues your credential; for MCP, the organisation enables the integration and you connect with your own account.

ScopomapPartner API reference