Developers

Build integrations with CAIRE

Choose the integration path for your work: inbound Carefox data, the CAIRE Partner API, or a human-operated MCP connection.

The API specification is shown in CAIRE for your environment.

CAIRE Partner API through Connect

The customer's Partner API is a separate integration path configured in CAIRE Connect; it differs from inbound Carefox data and human-operated MCP.

An organisation administrator configures the connection, client, scopes and unit allowlist.
Use the OpenAPI URL and scopes shown in CAIRE for your environment. Review data classes and explicitly grant access to each live unit.
Use idempotency keys where supported and retain receipts for each request. Revoke the client when access should end.

Carefox is a separate path for customer data arriving in CAIRE.

Use the Carefox flow for inbound data from a customer's Carefox environment. It is separate from CAIRE's Partner API.
Review the import receipt and summary in CAIRE. A planner reviews the input before accepting it or creating planning data.
For Carefox customers, journals remain in Carefox; CAIRE Connect does not mean journal data is natively stored in CAIRE.

Let a person use a compatible AI tool with their own CAIRE sign-in and permissions.

MCP is a human-operated connection for reading available planning data and preparing proposals. A person reviews and makes changes in CAIRE.
Copy the organisation URL from Settings → Integrations and follow the guide to connect an AI tool.
Available tools and data depend on the connected server version and the user's CAIRE permissions.