Development
Build integrations for a managed OrbitPage workspace using the public REST API, OpenAPI, n8n and approved MCP connections.
Last reviewed 15 October 2026SaaS development means building on the supported customer interfaces. Personal REST tokens, OAuth MCP connections and browser tools have different contracts. Use the API reference for exact fields, scopes and responses.
Choose the supported interface
Use the versioned Automation REST API for scripts and integrations, n8n for workflow nodes, and remote MCP for approved AI clients. Dashboard-only routes are internal and do not accept a personal REST token. The OSS server API is a different contract; self-hosted endpoint assumptions do not apply to SaaS.
Create a scoped connection
Create a personal token from Team for the intended workspace and grant only required scopes. Store its one-time secret on the server or in your workflow credential store. OAuth MCP instead uses sign-in and workspace approval; never substitute a personal REST token for that flow.
Read the contract and validate changes
The generated OpenAPI document and endpoint reference describe supported requests and responses. Read the current resource and revision, validate input, write with the required precondition and check whether the operation saves a draft or publishes. Plan and role checks still apply to automation.
Test and operate the integration
Start with a read-only call and a dedicated test workspace. Check errors, retries, pagination and credential revocation before enabling schedules. Keep request secrets and private responses out of logs. Use the OSS Development category when contributing to the shared editor; it documents the public repository, not access to the managed platform's infrastructure.