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 sandbox is advanced, and both of Zendesk's live pagination mechanisms including the deep-offset ceiling nobody models.
- Category
- Support
- Sandbox 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
Scenarios
Start a sandbox in one of these, or describe the state you want in a sentence and the seeder writes the records it implies.
Busy helpdesk
Two dozen tickets across every status, with comment histories, so pagination and search have real data on the first call.
Where is my order queue
A queue of “where is my order” tickets carrying order numbers in their bodies and in a custom field, which is the exact shape an ecommerce support agent is built for.
Closed ticket
A closed ticket and the follow-up that replaced it, so the immutability refusal and the correct recovery path are both there.
SLA breached
A ticket past its first-reply target, so escalation logic runs on the first call rather than never.
End user credential
The credential authenticates as an end user, so every agent-only call is a 403 — the most common real Zendesk integration failure after rate limits.
Rate limited
Ticket writes start throttled while reads flow, so a caller's backoff runs against a real Retry-After.
Pending bulk job
A queued update_many job whose effects are not visible yet, so a job_status poll loop is exercised.
What it models
Records your code can read, write and edit for the life of the sandbox. 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