CINNOX API

Name: CINNOX API API
Brand: CINNOX API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsChat Messagingbearer17 EndpointsREST

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.

Quickstart

Get started with CINNOX API 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:
"send a message to a CINNOX customer conversation"

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

Capabilities

What an agent can do with CINNOX API 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

GET STARTED

Start building with CINNOX API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for CINNOX API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use CINNOX API 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 MAXsystem 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

Why though Jentic?

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

Credential isolation

CINNOX bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access — the raw token never enters the agent's prompt or memory.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send a message to a customer') and Jentic returns the matching CINNOX operation with its JSON schema, so the agent can call the right endpoint without browsing CINNOX docs.

Time to first call

Direct CINNOX integration: 1-2 days for bearer auth, conversation threading, and error handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Circle Community Platform API

Circle manages community spaces while CINNOX handles 1:1 customer engagement.

Choose Circle when the goal is many-to-many community discussion; choose CINNOX when the goal is direct customer support across chat, SMS, and voice.

Alternative

Cisco Webex API

Webex provides enterprise messaging and meetings, overlapping CINNOX's chat surface.

Choose Webex inside Cisco-standardised enterprises; choose CINNOX when the priority is unifying external customer channels rather than internal collaboration.

Complementary

GoToMeeting API

GoToMeeting handles scheduled video sessions that complement CINNOX text and voice channels.

Use GoToMeeting to schedule a follow-up video call after CINNOX captures the inbound chat or SMS conversation.

FAQs

Specific to using CINNOX API 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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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. Sign up at https://app.jentic.com/sign-up.

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.