Appearance
API domains
The CoCoCo API is large — the published reference alone lists 335 queries and 497 mutations. Rather than read it end to end, start from the domain that matches what you are doing.
These fourteen domains are how the platform itself groups the schema — the MCP server exposes one schema/<domain> resource for each. Each one is a slice of the same API; the full reference has every published operation and type in detail.
| Domain | Covers | Start with |
|---|---|---|
| Production Floor | Jobs, components, operations, scheduling, production reporting, and the files attached to them. The largest domain. | listJobs, productionBoard |
| Order Intake | Quotes, estimates, orders, invoices, customers, products and pricing. | convertEstimateToOrder, createJobsFromOrder |
| Print Prepress | Substrates, imposition specs, preflight reports, prepress operations and artwork files. Product templates live here, because instantiation is a prepress concern. | |
| Fulfillment | Shipping, carriers, warehousing, stock and procurement. | |
| ERP Costing | Cost categories, centres, rates, operation cost mappings and recorded costs. | |
| Device Fleet | Controllers, devices, edge apps, networks, metrics, telemetry and JMF device binding. | |
| AI and ML | AI adapters and agents, chat sessions, knowledge notes, ML models and their configurations. | |
| App Authoring | Custom apps, dashboards, data schemas, records and clips. | |
| Workflow Authoring | Workflow definitions, versions, triggers, executions and expression validation. | |
| Administration and IAM | Policies, users, teams, API tokens, tenant configuration, logs and archives. Not part of the published reference; the console's API Docs page (/#/docs) lists these operations, and a connected agent sees them through the MCP server. | |
| Integrations | Integration definitions and instances, incoming webhooks and notification routing. | |
| Journeys and Workspaces | Journey and workspace definitions and their versions. | |
| Scripting | Tenant Lua scripts, custom actions and script validation. | |
| Reporting | Ad-hoc MicroSQL reporting queries and their schema description. The smallest domain. | describeQuerySchema, then reportQuery |
A few operations appear in every domain: the Magic Query family, the data change event feed, and ping.
Where to go next
- The full API reference — every query, mutation, subscription and type, generated from the live schema.
- Magic Query — a URI-style façade over the same data, for when a full GraphQL query is more than you need.
- Connecting an agent — point an AI agent at this API and let it find its own way around.