Kustomer API

Name: Kustomer 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.

Install Jentic One Beta

Connect the Kustomer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kustomer 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Kustomer 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

GET STARTED

Start building with Kustomer API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Kustomer 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 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.

FAQs

Specific to using Kustomer 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.

Kustomer API

Connect the Kustomer API to your agent

Capabilities

Start building with Kustomer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs