Udesk, the flagship product of Beijing Wofeng Times Data Technology (沃丰科技/Wofeng Technology), is a Chinese intelligent customer service and customer-experience platform serving enterprises like Yili, BYD, Schneider Electric, and China Merchants Group. The suite spans omnichannel IM (20+ channels including WeChat, Weibo, and mini-programs), ticketing, a cloud call center with CC PaaS APIs, GaussMind LLM-powered chat/voice robots, ServiceGo field-service management, KCS knowledge management, and video customer service. Its developer center publishes REST-style Open APIs (v2 recommended, v1 legacy), event-callback webhooks, and mobile/web SDKs, all tenant-scoped with signed-request authentication.
Udesk is listed with 5 APIs on the APIs.io network. Tagged areas include Company, Enterprise, Customer Service, Call Center, and Ticketing.
The Udesk catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Udesk’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, authentication, and 20 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
AI & Biometrics regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/udesk/"><img src="https://apis.io/badge/udesk/card.svg" alt="Udesk on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
The recommended tenant-scoped Open API for customers, tickets, organizations, agents, agent groups, departments, knowledge base, IM sessions, call center, outbound call tasks, q...
Legacy Open API kept for existing integrations (tickets, customers, IM, call center, help center) with MD5 query-string signature auth; the docs recommend migrating to v2.
Bot platform API for applications and robots, FAQ knowledge bases, bot sessions, task-flow entities, external LLM integration, and the robot webhook integration hook.
Knowledge center service API for knowledge spaces, categories, Q&A knowledge items, and file knowledge, authenticated with a 50-minute Bearer token from /api/auth/open/token.
Event surface derived from Udesk's published webhook documentation (Udesk ships no AsyncAPI of its own). Three webhook families are documented: - **Open API event callbacks (web...
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.