Introduction
The API reference documents the HTTP operations available for direct integrations. The CLI and MCP expose subsets of these operations, with different discovery, input, and job-handling behavior. An endpoint appearing here does not mean it has a CLI command or is enabled on every MCP connection.
Choose an interface
The published CLI 1.8.0 supports creative projects and items but does not have dedicated commands for PM boards, workflow management, agent management, or knowledge bases. MCP availability also depends on the connection’s tool inventory.
Find the right API
Creative projects and PM boards are separate resources. The former uses project and item operations; the latter uses board, status, and task operations. A project item ID is not a task ID. See Organize and automate for a practical example using both.
The other API sections cover workspace identity, brand context, assets, generation, social publishing and analytics, media processing, and notifications.
Base URLs
Most operations use:
Agents and Knowledge Bases use:
The same workspace credential works with both services. Use the server and path shown on the individual endpoint page.
Make your first integration
- Create an API key and authenticate.
- Identify the workspace and select a space.
- Read the endpoint’s required parameters and request schema.
- Submit the request and keep the returned identifiers.
- For background work, follow Async jobs and polling and the endpoint’s documented completion state.
HTTP schemas describe the direct API call. An MCP tool may add convenience inputs or follow-up behavior; use the current tool schema when calling MCP rather than assuming every tool argument belongs in the REST body.
