API — Overview

OmniCon ships a JSON REST API at https://api.omnicon.cloud. It covers almost the same surface as the web dashboard — articles, pages, books, press releases, media, channels, authors, memberships — so you can build your own frontend, run bulk imports, or wire OmniCon into another system without touching the editor.

When to use the API vs. the other options

• API — scripts, backends, custom frontends, mobile apps, CI pipelines. You control the request flow.
• MCP server — driving OmniCon from Claude or another MCP client in natural language. Same capabilities, different transport.
• Dashboard — day-to-day authoring in a browser.

The API and MCP server share the same underlying services and the same identity system, so a token issued for one works with the other.

What's in this section

• Authentication — how to get a JWT and include it on requests.
• Endpoints — the full surface area grouped by resource.
• Examples — copy-paste curl flows for the most common tasks.

Quick facts

• Base URL: https://api.omnicon.cloud
• Transport: HTTPS, JSON request and response bodies.
• Auth: JWT bearer tokens. Get one from POST /api/auth/login.
• Interactive docs: Swagger UI at https://api.omnicon.cloud/, raw OpenAPI spec at /swagger/v1/swagger.json.
• Content types: application/json for most endpoints, multipart/form-data for file uploads.

How it relates to channels

Every resource the API manages belongs to a channel, and channels belong to organizations. Almost every request takes a channelId (or an organizationId) to scope the call — the token identifies who you are, and the channel ID identifies where the work happens. Your token has to have access to the channel you're operating on, otherwise the call is rejected.

Start with Authentication to get a token, then jump to Examples for working curl flows you can adapt.