Zendesk
live · conformance passing
Models the Zendesk Support API a helpdesk integration actually uses — tickets through the whole status machine with server-set descriptions, public and private comments, requesters created implicitly from an email address, users and organizations with create_or_update, groups and the assignment rules between them, search over Zendesk's query grammar, macros, derived ticket metrics and incremental exports — with API-token and OAuth authentication, role and scope refusals, per-endpoint rate limits carrying real Retry-After headers, bulk jobs that stay queued until the environment is advanced, and both of Zendesk's live pagination mechanisms including the deep-offset ceiling nobody models.
- Category
- Support
- Environment key
- a 40-character token, no prefix
- Verified against
- https://developer.zendesk.com/zendesk/oas.yaml 2.0.0
- Replaces
- A Zendesk trial that locks after fourteen days
What it models
Records your code can read, write and edit for the life of the environment. A route the twin does not model returns a provider-shaped refusal rather than a plausible response.
- account
- tickets
- comments
- users
- organizations
- groups
- group_memberships
- macros
- satisfaction_ratings
- ticket_fields
- ticket_metrics
- job_statuses
Verified in CI against
- openapihttps://developer.zendesk.com/zendesk/oas.yaml2.0.0