Zendesk Support API
CRMCustomer Supportbasic489 EndpointsREST
For Agents
Programmatically list assignable groups and agents based on query matched against name, list assignable groups on the assigneefield. Covers 489 operations with basic authentication.
Use for: I need to assignable groups and agents based on query matched against name, I want to assignable groups on the assigneefield, Search for assignable agents from a group on the assigneefield, Find all sources by target
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Zendesk Support API endpoints. The API exposes 489 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Support API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Support 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%2Fzendesk.com%2Fzendesk" | 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%2Fzendesk.com%2Fzendesk" | 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 Support API.
List assignable groups and agents based on query matched against name
Get sources by target
Show Settings
Update Account Settings
Create Trial Account
Use Cases
Patterns agents use Support API for, with concrete tasks.
★ CRM Operations
Use the Support API to perform crm operations programmatically. The API provides 489 endpoints covering core functionality including list assignable groups and agents based on query matched against name, list assignable groups on the assigneefield, list assignable agents from a group on the assigneefield.
Call GET /api/lotus/assignables/autocomplete.json to list assignable groups and agents based on query matched against name
Automated Attachments Management
Automate attachments operations by combining multiple Support API endpoints. Agents can list assignable groups on the assigneefield and then list assignable agents from a group on the assigneefield in a single workflow.
Call GET /api/lotus/assignables/groups.json to list assignable groups on the assigneefield, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Support API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.
Search Jentic for 'list assignable groups and agents based on query matched against name', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
489 endpoints — zendesk support api endpoints.
METHOD
PATH
DESCRIPTION
GET
/api/lotus/assignables/autocomplete.json
List assignable groups and agents based on query matched against name
GET
/api/lotus/assignables/groups.json
List assignable groups on the AssigneeField
GET
/api/lotus/assignables/groups/{group_id}/agents.json
List assignable agents from a group on the AssigneeField
GET
/api/v2/{target_type}/{target_id}/relationship_fields/{field_id}/{source_type}
Get sources by target
GET
/api/v2/account/settings
Show Settings
PUT
/api/v2/account/settings
Update Account Settings
POST
/api/v2/accounts
Create Trial Account
GET
/api/v2/accounts/available
Verify Subdomain Availability
GET
/api/lotus/assignables/autocomplete.json
List assignable groups and agents based on query matched against name
GET
/api/lotus/assignables/groups.json
List assignable groups on the AssigneeField
GET
/api/lotus/assignables/groups/{group_id}/agents.json
List assignable agents from a group on the AssigneeField
GET
/api/v2/{target_type}/{target_id}/relationship_fields/{field_id}/{source_type}
Get sources by target
GET
/api/v2/account/settings
Show Settings
PUT
/api/v2/account/settings
Update Account Settings
POST
/api/v2/accounts
Create Trial Account
GET
/api/v2/accounts/available
Verify Subdomain Availability
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Zendesk Support API by hand means encoding its basic auth on every request, filling in your {subdomain}.{domain}.com host, and coding request handling across hundreds of endpoints yourself. Through Jentic you install once, import Support from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The Support API puts resource ids in the URL path (for example /assignables/groups/{group_id}/agents.json and relationship fields keyed by target id), so a rule can pin your agent to one group or account resource. You choose the operations it may call, so writes like updating account settings are not included unless you add them.
Credential isolation
Your Zendesk credential 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 'list assignable groups' or 'read account settings', and Jentic returns the matching Support 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 Support API through Jentic.
What authentication does the Support API use?
The Support API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I list assignable groups and agents based on query matched against name with the Support API?
Yes. Use the GET /api/lotus/assignables/autocomplete.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Support API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list assignable groups and agents based on query matched against name through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list assignable groups and agents based on query matched against name'. Jentic returns the matching Support API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Support API have?
The Support API exposes 489 endpoints covering attachments, sessions, trigger categories operations.
Can I limit what my agent is allowed to do with the Zendesk Support API?
Yes. Jentic One runs self-hosted, so your own rules decide which Support API operations and credentials the agent may use. Because the API keys resources by id in the URL path, such as /api/lotus/assignables/groups/{group_id}/agents.json and relationship fields keyed by target id, you can pin the agent to a single group or account resource. You also choose which operations it may call, so writes like Update Account Settings (PUT /api/v2/account/settings) or Create Trial Account stay off limits unless you explicitly allow them.
GET STARTED