Kustomer API

Name: Kustomer API API
Brand: Kustomer API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer Supportbearer19 EndpointsREST

For Agents

Manage Kustomer customer service: read and update customers, create or route conversations, post messages, attach notes, and pull audit logs.

Quickstart

Get started with Kustomer 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:
"create a Kustomer conversation"

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

Capabilities

What an agent can do with Kustomer API API.

Create or update a customer record via POST /customers and PUT /customers/{id} including identity, attributes, and tags

Open new support conversations with POST /conversations and update assignment or status via PUT /conversations/{id}

Post a reply or internal message into a conversation through POST /messages tied to the parent conversation ID

Attach internal notes to customers and conversations via POST /notes for handoff context

GET STARTED

Start building with Kustomer API API

Explore with Jentic

View OpenAPI Document

Use for: I need to create a new customer in Kustomer, I want to open a support conversation for a known customer, Post a reply message into an existing Kustomer conversation, Update the status of a conversation to closed

Not supported: Does not handle billing, marketing automation, or product analytics — use for customer support and conversational CRM only.

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

Jentic publishes the only available OpenAPI specification for Kustomer API, keeping it validated and agent-ready. Kustomer is a customer experience platform combining CRM and conversational support. The API exposes customers, conversations, messages, companies, notes, brands, and audit logs as REST resources, authenticated with a bearer token. Agents can list and update customer records, create and route conversations, post messages into existing threads, and pull audit logs for compliance reporting.

Use Cases

Patterns agents use Kustomer API API for, with concrete tasks.

★ Inbound Ticket Triage

Triage inbound conversations as they land in Kustomer. Agents read the conversation via GET /conversations/{id}, classify it from the message body, and PUT /conversations/{id} to set assignee, priority, or status. The customer record is updated via PUT /customers/{id} with any new attributes inferred from the message, all tied together by the customer and conversation IDs.

On a new conversation event, GET /conversations/{id} to fetch context, classify the topic, and PUT /conversations/{id} with assigneeUsers and priority set.

Unified Customer Profile Sync

Keep Kustomer customer profiles in sync with the system of record. When a customer record changes upstream (in billing, identity, or product), POST /customers or PUT /customers/{id} pushes the change into Kustomer so support agents always see current data, with companies linked via /companies.

On a customer.updated event from billing, look up the matching Kustomer customer by email and PUT /customers/{id} with new plan, lifetime value, and last-seen attributes.

Compliance Audit Reporting

Pull audit logs from Kustomer to feed a compliance reporting pipeline. GET /audit-logs returns recent actions across the workspace, which can be filtered, summarised, and routed into a SIEM or governance dashboard. Notes posted via /notes provide additional human-readable context where the audit log is sparse.

GET /audit-logs filtered to the past 24 hours, summarise by user and action, and post the summary into a compliance Slack channel.

AI Agent Customer Support Copilot

A copilot embedded in a support agent's view drafts replies, posts internal notes, and updates conversation status from natural language. Through Jentic, the copilot calls Kustomer by intent without storing the bearer token in the agent runtime.

On 'reply that we'll refund and close the ticket', POST /messages with the drafted reply and PUT /conversations/{id} to set status to done.

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for kustomer api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/customers

Create a customer

PUT

/customers/{id}

Update a customer

POST

/conversations

Open a new conversation

PUT

/conversations/{id}

Update conversation status or assignment

POST

/messages

Post a message into a conversation

POST

/notes

Attach an internal note

GET

/audit-logs

List audit log entries

POST

/customers

Create a customer

PUT

/customers/{id}

Update a customer

POST

/conversations

Open a new conversation

PUT

/conversations/{id}

Update conversation status or assignment

POST

/messages

Post a message into a conversation

POST

Why though Jentic?

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

Credential isolation

Kustomer bearer tokens are stored encrypted in the Jentic MAXsystem vault. Agents call Kustomer through Jentic without ever seeing the raw token.

Intent-based discovery

Agents search by intent (e.g. 'create a Kustomer conversation' or 'update a customer') and Jentic returns the matching operation with its input schema.

Time to first call

Direct Kustomer integration: 1-2 days for auth, pagination, and conversation modelling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Zendesk API

Established support platform with broader channel coverage than Kustomer.

Choose Zendesk when the team is already on Zendesk or needs deeper macro and trigger automation.

Alternative

Intercom API

Conversational support and messaging platform with strong outbound features.

Choose Intercom when proactive messaging and product tours are part of the support surface.

Alternative

Freshdesk API

Help desk platform with a similar resource model to Kustomer.

Choose Freshdesk when ticketing-first workflows take priority over the unified CRM model Kustomer offers.

Complementary

Help Scout API

Email-first support tool used alongside Kustomer in some smaller teams.

Use Help Scout when an agent needs to bridge email-only support workflows into a Kustomer-centric CRM.

FAQs

Specific to using Kustomer API API through Jentic.

Why is there no official OpenAPI spec for Kustomer API?

Kustomer does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kustomer 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 Kustomer API use?

Kustomer uses HTTP bearer authentication: every request needs an Authorization header with a Kustomer-issued token. Through Jentic, the token is stored encrypted in the MAXsystem vault.

Can I post a message into an existing Kustomer conversation?

Yes. POST /messages accepts a parent conversation ID and a message body, and creates a new message inside that conversation. Use PUT /conversations/{id} alongside it to change status or assignee in the same flow.

How do I close a support conversation through Jentic?

Search Jentic for 'update Kustomer conversation status'. Jentic returns PUT /conversations/{id} with its schema. Provide the conversation ID and the desired status, and Jentic executes the call using the stored bearer token.

What are the rate limits for the Kustomer API?

Public rate limits are not exposed in the spec. Refer to developer.kustomer.com for the current limits and burst behaviour for your plan before scaling agent traffic.

Does the Kustomer API expose audit logs?

Yes. GET /audit-logs returns a paginated stream of workspace activity, suitable for compliance reporting and feeding a SIEM. Filter parameters in the response let you narrow by date and actor.