Enchant API

Name: Enchant API
Brand: Enchant API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer Supportbearer17 EndpointsREST

For Agents

Manage helpdesk tickets, replies, customers, labels, and inboxes in Enchant from external tools or agents.

Install Jentic One Beta

Connect the Enchant API to your agent

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

Create, list, retrieve, update, and delete support tickets in any inbox

Post replies to a ticket and read the existing reply thread

Create and update customer records and read their associated tickets

GET STARTED

Start building with Enchant API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Enchant API for, with concrete tasks.

★ External Channel to Helpdesk Bridge

Convert messages from chat apps, social channels, or product feedback forms into Enchant tickets so support stays consolidated. The API exposes POST /tickets to create the ticket and POST /tickets/{ticketId}/replies to append agent or customer messages. Support operations teams use this to centralise their queue while keeping users in the channel they prefer.

POST /tickets with the customer email and message body, then POST /tickets/{ticketId}/replies for follow-up turns from the source channel.

Customer 360 Sync

Sync customer records and ticket history into a CRM or analytics tool to give account teams a complete view of support history. The API supports listing customers, retrieving a single record with tickets, and updating contact fields, so a sync job can keep both systems aligned. Customer success and account teams use this to brief themselves before renewal calls.

Iterate GET /customers, then GET /customers/{customerId}/tickets per customer to compose a support history payload for the CRM sync.

Automated Ticket Triage

Automatically tag and route incoming tickets using labels and inbox metadata so agents pick from a clean queue. The API exposes labels, inboxes, and the ticket update endpoint together. Support engineering teams use this to push triage logic out of brittle email rules and into a programmable layer.

Call GET /labels and GET /inboxes to build the routing table, then PUT /tickets/{ticketId} to apply labels and reassign the ticket.

Agent-Driven First-Response

An agent watches new tickets, drafts a first response from a knowledge base, and posts the reply via Enchant when it is confident — escalating to a human otherwise. Through Jentic the agent searches by intent, loads the schemas, and executes the calls without bespoke client code. First-response time on routine tickets drops from hours to minutes.

Search Jentic for 'reply to a support ticket', execute GET /tickets to find unanswered tickets and POST /tickets/{ticketId}/replies with the drafted response when the confidence threshold is met.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/tickets

List tickets with filtering

POST

/tickets

Create a new ticket

PUT

/tickets/{ticketId}

Update a ticket

POST

/tickets/{ticketId}/replies

Reply to a ticket

GET

/customers/{customerId}/tickets

List tickets for a customer

GET

/labels

List labels

GET

/inboxes

List inboxes

GET

/tickets

List tickets with filtering

POST

/tickets

Create a new ticket

PUT

/tickets/{ticketId}

Update a ticket

POST

/tickets/{ticketId}/replies

Reply to a ticket

GET

/customers/{customerId}/tickets

List tickets for a customer

GET

Why Jentic?

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

Credential isolation

Enchant API tokens are stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw bearer never enters the agent's context, and Jentic injects it at execution time.

Intent-based discovery

Agents search by intent (e.g., 'create a helpdesk ticket') and Jentic returns matching Enchant operations with their input schemas, so the agent calls the right endpoint without reading docs.

Time to first call

Direct Enchant integration: 1-2 days for client code, auth handling, and pagination across tickets and customers. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Enchant API through Jentic.

Why is there no official OpenAPI spec for Enchant API?

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

The API uses HTTP Bearer authentication. Send the API token in the Authorization header on every request. Through Jentic the token is held encrypted in the vault and injected at execution time, so it never enters an agent's context.

Can I reply to a ticket programmatically with the Enchant API?

Yes. POST /tickets/{ticketId}/replies appends a reply to the ticket thread. The reply is delivered to the customer through the same channel as the original ticket.

How do I list a customer's tickets through Jentic?

Search Jentic for 'list a customer's helpdesk tickets', load the schema for GET /customers/{customerId}/tickets, and execute it with the customer ID returned by GET /customers.

What are the rate limits for the Enchant API?

The OpenAPI spec does not declare quantitative rate limits; Enchant enforces limits at the account level. Treat HTTP 429 responses as authoritative and back off using the Retry-After header where present.

Can I tag tickets with labels via the API?

Yes. GET /labels lists available labels, and PUT /tickets/{ticketId} applies them to a ticket alongside other field updates.

Enchant API

Connect the Enchant API to your agent

Capabilities

Start building with Enchant API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs