A
AEO Score: 0.70 / 1.00

Zendesk

Customer Support
Good — Functional agent integration
Agent Ready
Connectable
MCP Type
Third-party
Success Rate
🔴 Low
Agent Activity
●● Moderate
Recipes
✓ Available

Get Full Integration Guide

Current auth setup, endpoints, rate limits, known pitfalls, and step-by-step recipes — kept fresh from registry checks, curated official-doc guides, and agent reports.

npx @kansei-link/mcp-server

Then use: search_servicesget_service_detail

How to Connect Zendesk to an AI Agent

Auth setup

1. Admin Center > Apps and integrations > APIs > Zendesk API. 2. Enable Token Access. 3. Add API Token. 4. Use Basic Auth: base64({email}/token:{api_token}).

Key facts

Base URLhttps://{subdomain}.zendesk.com/api/v2/
API versionv2
AuthThree methods: 1) API Token — generate in Admin > Channels > API. Use as {email}/token:{api_token} with Basic Auth. 2) OAuth 2.0 for third-party apps. 3) Password auth (not recommended). API Token is simplest for agents.
Token URLhttps://{subdomain}.zendesk.com/oauth/tokens
Scopesread,write
Request bodyapplication/json
Paginationcursor-based: response has 'meta.has_more' and 'links.next'. Use CBP (cursor-based pagination) for /tickets. Offset pagination being deprecated.
Rate limit400 requests/minute (Team), 700/min (Professional), 2500/min (Enterprise). HTTP 429 with Retry-After header.
Error formatJSON: {"error":"RecordNotFound","description":"Not found"}

Key endpoints

MethodPathDescription
GET/ticketsList tickets with filters (status, assignee, etc.)
POST/ticketsCreate a new ticket
PUT/tickets/{id}Update ticket (status, assignee, tags, etc.)
GET/search.json?query={query}Search tickets, users, organizations
GET/users/{id}Get user/requester details
GET/tickets/{id}/commentsGet ticket conversation history

Quickstart

GET /api/v2/tickets?status=open&sort_by=created_at&sort_order=desc HTTP/1.1
Host: mycompany.zendesk.com
Authorization: Basic {base64(email/token:api_token)}
Accept: application/json

Response: {"tickets":[{"id":123,"subject":"ログインできない","status":"open","requester_id":456}]}

Agent pitfalls & tips

Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-04. Specs change — verify against the official docs before production use.

Frequently Asked Questions

What is Zendesk's AEO score?
Zendesk has an AEO score of 0.70 and is rated A (Functional agent integration). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Zendesk AI-agent-ready?
Zendesk is currently connectable for AI agent use. Third-party MCP integrations are available for this service. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Zendesk compare to other Customer Support services?
In the Customer Support category, Zendesk is rated A. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Zendesk compares.
How can I integrate Zendesk with an AI agent?
The fastest way to integrate Zendesk with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Zendesk?
Three methods: 1) API Token — generate in Admin > Channels > API. Use as {email}/token:{api_token} with Basic Auth. 2) OAuth 2.0 for third-party apps. 3) Password auth (not recommended). API Token is simplest for agents. Setup: 1. Admin Center > Apps and integrations > APIs > Zendesk API. 2. Enable Token Access. 3. Add API Token. 4. Use Basic Auth: base64({email}/token:{api_token}).
What are Zendesk's API rate limits?
400 requests/minute (Team), 700/min (Professional), 2500/min (Enterprise). HTTP 429 with Retry-After header.