CINNOX API
Agent-ready OpenAPI document · curated by JenticCommunicationsChat Messagingbearer17 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage omnichannel customer conversations, contacts, channels, and team routing on CINNOX. Send and retrieve messages, create contacts, and configure communication channels through 17 REST endpoints.
Use for: I need to create a new CINNOX contact for an inbound lead, Send a chat message into an existing CINNOX conversation, Retrieve the full message history for a customer conversation, List all communication channels configured in my CINNOX tenant
Not supported: Does not handle billing, marketing automation, or video conferencing - use for omnichannel customer messaging and contact management only.
Jentic publishes the only available OpenAPI specification for CINNOX API, keeping it validated and agent-ready. CINNOX is an omnichannel customer engagement platform that unifies voice, chat, SMS, and social channels into a single conversation thread per contact. The API exposes contact records, conversation timelines, individual messages, channel configuration, and team routing across 17 endpoints under https://api.cinnox.com/v1. Authentication uses a bearer token, and operations are organised around five core resources: Contacts, Conversations, Messages, Channels, and Teams.
Install Jentic One Beta
Connect the CINNOX API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CINNOX API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcinnox.com%2Fcinnox" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcinnox.com%2Fcinnox" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with CINNOX API.
Create contact records and update profile details for omnichannel customer engagement
Retrieve conversation threads including merged history across voice, chat, and SMS channels
Post outbound messages into a specific CINNOX conversation by conversationId
List and configure communication channels available to your CINNOX tenant
Provision support teams and assign agents for routing inbound conversations
Look up an individual contact by contactId to fetch profile and engagement metadata
Delete an obsolete channel configuration to retire a communication endpoint
Use Cases
Patterns agents use CINNOX API for, with concrete tasks.
★ Unified Inbound Customer Conversations
Pull every inbound interaction a customer has had across chat, voice, SMS, and social into a single thread for review or AI summarisation. The CINNOX API exposes /conversations and /conversations/{conversationId}/messages so a service desk agent or AI copilot can fetch the full omnichannel history for one contact in a single call. This replaces stitching together separate channel logs and supports tenants with thousands of monthly conversations.
Fetch all messages from CINNOX conversation conv_abc123 via GET /conversations/conv_abc123/messages and summarise the customer's last three issues.
Contact Sync With External CRM
Keep a CINNOX customer directory in sync with an external CRM like Salesforce or HubSpot by creating contacts on inbound, updating profile fields when CRM data changes, and retrieving contact details on demand. The /contacts endpoints support full CRUD against the contactId primary key, suitable for nightly sync jobs or event-driven webhooks.
Create a CINNOX contact for jane.doe@example.com via POST /contacts then update their profile with the company name pulled from HubSpot.
Outbound Messaging From a Workflow
Trigger an outbound chat or SMS to a CINNOX contact from any backend workflow, for order updates, appointment reminders, or support follow-ups. POST /conversations/{conversationId}/messages accepts a message body and posts it into the existing thread, preserving omnichannel context for the receiving agent.
Post the message 'Your order has shipped - tracking 1Z999' into CINNOX conversation conv_abc123 via POST /conversations/conv_abc123/messages.
AI Agent Conversation Drafting
An AI agent invoked through Jentic can read a CINNOX conversation, draft a reply, and post it back into the thread without holding raw bearer credentials. Jentic handles the bearer token in your Jentic One instance and routes the agent's structured request to GET and POST endpoints under /conversations. Integration takes minutes via Jentic versus the day or two needed to build direct OAuth and rate-limit handling.
Search Jentic for 'send a message in CINNOX', load the POST /conversations/{conversationId}/messages schema, then post a drafted response into conversation conv_abc123.
Key Endpoints
17 endpoints — jentic publishes the only available openapi specification for cinnox api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/contacts
List contacts in the CINNOX tenant
POST
/contacts
Create a new contact record
GET
/conversations
List conversations across all channels
GET
/conversations/{conversationId}/messages
Fetch messages within a conversation
POST
/conversations/{conversationId}/messages
Post a new message into a conversation
GET
/channels
List configured communication channels
POST
/teams
Create a support team for conversation routing
GET
/contacts
List contacts in the CINNOX tenant
POST
/contacts
Create a new contact record
GET
/conversations
List conversations across all channels
GET
/conversations/{conversationId}/messages
Fetch messages within a conversation
POST
/conversations/{conversationId}/messages
Post a new message into a conversation
GET
/channels
List configured communication channels
POST
/teams
Create a support team for conversation routing
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring CINNOX by hand means learning its bearer token auth and threading contacts, conversations, and messages through its omnichannel endpoints yourself. Through Jentic you install once, import the CINNOX API from the API Directory, store the token once, and your agent calls it.
Permission scoping
CINNOX puts the conversation id in the URL path (/conversations/{conversationId}/messages), so a rule can pin your agent to reading and posting messages in a given conversation. You choose the operations it may call, so contact creation or team setup is not included unless you add it.
Credential isolation
Your CINNOX token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send a message in a conversation' or 'look up a contact', and Jentic returns the matching CINNOX operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using CINNOX API through Jentic.
Why is there no official OpenAPI spec for CINNOX API?
CINNOX does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CINNOX API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the CINNOX API use?
The CINNOX API uses HTTP bearer authentication. Every request must include an Authorization: Bearer <token> header. Through Jentic, the bearer token is stored encrypted in your Jentic One instance and never exposed to the agent's context - Jentic injects it server-side at execution time.
Can I send outbound messages with the CINNOX API?
Yes. POST /conversations/{conversationId}/messages accepts a message body and posts it into an existing conversation thread. The thread retains omnichannel context, so a chat reply, SMS, or social message all flow through the same endpoint scoped by channel configuration.
What are the rate limits for the CINNOX API?
CINNOX does not publish rate limits in the OpenAPI spec. Standard tenant-level throttling applies - confirm specific limits with your CINNOX account manager. Jentic surfaces 429 responses back to the agent so retries can be scheduled cleanly.
How do I post a message into a CINNOX conversation through Jentic?
Run pip install jentic, then search Jentic for 'send a message in CINNOX'. Jentic returns the POST /conversations/{conversationId}/messages operation with its input schema. Load it, supply the conversationId and message body, and execute - Jentic handles the bearer token. Get started with Jentic One, the self-hosted execution layer.
Can I manage CINNOX contacts via the API?
Yes. The /contacts resource supports full lifecycle management: GET /contacts to list, POST /contacts to create, GET /contacts/{contactId} to read, PUT /contacts/{contactId} to update, and DELETE /contacts/{contactId} to remove. This makes the API suitable for syncing CINNOX with an external CRM.
Can I limit what my agent is allowed to do with the CINNOX API?
Yes. Because you run Jentic One yourself, your own rules decide which CINNOX operations and credentials the agent may use. CINNOX puts the conversation id in the URL path, such as POST /conversations/{conversationId}/messages, so you can pin the agent to reading and posting messages within a single conversation. You choose the operations it may call, so higher-impact actions like creating contacts via POST /contacts or provisioning teams via POST /teams stay out of reach unless you explicitly allow them.
GET STARTED