Cenit IO - REST API Specification

✓ Official Vendor SpecDeveloper ToolsCi CdapiKey40 EndpointsREST

For Agents

Build and run integration flows in Cenit IO programmatically — manage connections, data types, flows, schedulers, and event observers in the open-source iPaaS platform.

Quickstart

Get started with Cenit IO - REST API Specification in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an integration flow in Cenit IO"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cenit IO - REST API Specification API.

Manage iPaaS connections to external systems via /setup/connection endpoints

Define and update data types that describe the records flowing through Cenit

Build flows that route data between connections and apply translators

Configure schedulers to run flows on a recurring cadence

GET STARTED

Start building with Cenit IO - REST API Specification API

Explore with Jentic

View OpenAPI Document

Use for: I need to create a new connection to a third-party system in Cenit IO, Build a flow that transforms records between two data types, Schedule a flow to run hourly via the scheduler endpoint, Register an event observer that triggers on incoming data

Not supported: Does not handle hosted execution of arbitrary code, payment processing, or end-user authentication for downstream apps — use for managing integration pipeline configuration in Cenit IO only.

Cenit IO is an open-source integration platform (iPaaS) for moving data between business systems. The REST API exposes the platform's setup primitives — connections, connection roles, data types, flows, namespaces, observers (events), and schedulers — so external clients can build, modify, and orchestrate integration pipelines programmatically. The same API surface that the Cenit IO web UI uses is available here for automation. Authentication requires both an X-User-Access-Key and an X-User-Access-Token header.

Use Cases

Patterns agents use Cenit IO - REST API Specification API for, with concrete tasks.

★ Programmatic iPaaS Pipeline Build-Out

Integration teams script the creation of dozens of similar pipelines — for example one per customer tenant — by calling the Cenit setup endpoints in sequence. An agent or template runner posts connections, data types, flows, and schedulers from a configuration file, removing the click-through cost of standing up each tenant in the Cenit UI.

POST /setup/connection, then /setup/data_type, then /setup/flow with the configuration for a new tenant pipeline

Scheduled Data Sync Configuration

Operations teams use Cenit to run nightly syncs between a CRM and a data warehouse. Rather than configure schedulers in the UI, an agent posts the schedule definitions via /setup/scheduler and binds them to existing flows, then verifies the schedule with a GET. This keeps schedule changes versionable in source control.

POST /setup/scheduler with a cron expression, then GET /setup/scheduler/{id} to confirm it is bound to the right flow

Event-Driven Flow Triggers

Cenit observers (events) trigger flows on inbound conditions such as a new record matching a filter. An agent provisions observers via /setup/observer, references the upstream data type, and verifies the binding. This brings event-driven integration patterns into existing flow definitions.

POST /setup/observer with the data type id and filter expression, then list observers via GET /setup/observer/ to confirm

AI Agent Integration via Jentic

An integration agent uses Jentic to discover Cenit IO endpoints, load schemas for setup operations, and execute calls without holding the access key and token directly. This is useful when an LLM-driven agent reasons over user requests like 'add a Stripe-to-warehouse sync' and needs to provision the underlying iPaaS pipeline programmatically.

Use Jentic to search 'create a Cenit IO flow', load the schema for POST /setup/flow, and execute with the source and destination data type ids

Key Endpoints

40 endpoints — cenit io is an open-source integration platform (ipaas) for moving data between business systems.

METHOD

PATH

DESCRIPTION

GET

/setup/connection

List connections

POST

/setup/connection

Create or update a connection

POST

/setup/flow/

Create or update a flow

POST

/setup/data_type/

Create or update a data type

POST

/setup/scheduler/

Create or update a scheduler

POST

/setup/observer/

Create or update an event observer

GET

/setup/namespace/

List namespaces

GET

/setup/connection

List connections

POST

/setup/connection

Create or update a connection

POST

/setup/flow/

Create or update a flow

POST

/setup/data_type/

Create or update a data type

POST

/setup/scheduler/

Create or update a scheduler

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Cenit IO X-User-Access-Key and X-User-Access-Token values are stored encrypted in the Jentic vault. Agents call /setup endpoints through scoped execution requests; neither header value enters the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'create an integration flow in Cenit') and Jentic returns the matching /setup operations with their input schemas, so the agent doesn't have to navigate the 40-endpoint surface manually.

Time to first call

Direct Cenit IO integration: 2-3 days mapping the setup model and configuring auth. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

n8n API

Open-source workflow automation platform with similar self-hosting story

Choose n8n when the customer wants a node-based workflow editor; choose Cenit when the customer wants a data-type-first iPaaS approach

Alternative

Zapier NLA API

Hosted automation platform with a vast app library and natural-language actions

Choose Zapier when the customer wants a hosted iPaaS with a wide app library; choose Cenit when self-hosting and openness matter

Complementary

cdnjs API

Lookup utility commonly invoked from integration flows that handle web assets

Pair cdnjs with Cenit when an integration flow needs to enrich a record with the latest CDN-hosted asset URL

FAQs

Specific to using Cenit IO - REST API Specification API through Jentic.

What authentication does the Cenit IO API use?

Cenit IO requires two header values together: `X-User-Access-Key` and `X-User-Access-Token`, both issued from a user's Cenit account. Through Jentic both values are stored encrypted in the vault and injected at execution time.

Can I build integration flows programmatically with Cenit?

Yes. The /setup/flow, /setup/connection, /setup/data_type, /setup/scheduler, and /setup/observer endpoints together cover the full setup needed for an integration pipeline — flows can be built, scheduled, and event-triggered without touching the Cenit UI.

What are the rate limits for the Cenit IO API?

The OpenAPI spec does not declare specific numeric rate limits. Cenit IO is open source and self-hostable, so limits depend on the deployment. On the public hosted instance, treat as fair-use and back off on 429 responses.

How do I create a Cenit flow through Jentic?

Search Jentic for 'create a Cenit IO flow', load the schema for POST /setup/flow/, and execute with source and destination data type ids. Schedule it via POST /setup/scheduler in the same agent run.

Is the Cenit IO API free?

Cenit IO is open source under the MIT licence and self-hostable for free. The hosted cenit.io service offers tiered plans listed on the website; the API itself has no separate cost beyond the chosen plan.

Can I organise integrations by project or tenant?

Yes. The /setup/namespace endpoints let you group flows, data types, and connections under named namespaces, which is the recommended pattern for multi-tenant or per-project setups.