{ "totalCount": 42, "tickets": [ { "id": "b3e1f9a0-1234-4abc-9def-567890abcdef", "status": "open", "resolutionStatus": "unresolved", "channelType": "email", "title": "Order not received", "summary": "Customer reports their order #12345 has not arrived after 10 days.", "priority": 2, "sentiment": -0.6, "language": "en", "assigneeId": "a1b2c3d4-5678-9abc-def0-1234567890ab", "teamId": "f0e1d2c3-b4a5-6789-0abc-def123456789", "endCustomerId": "cust-001", "endCustomerName": "Jane Doe", "endCustomerEmail": "jane.doe@example.com", "endCustomerWaitingForReplySince": "2026-03-15T14:30:00Z", "csatRating": 4, "csatComment": "Quick response, still waiting for resolution.", "variables": { "orderId": "ORD-12345", "accountType": "premium" }, "createdAt": "2026-03-14T09:00:00Z", "updatedAt": "2026-03-15T14:30:00Z" } ]}
Integrations
Tickets API
Retrieve tickets programmatically with filtering, sorting, and pagination.
Fetch tickets from your Typewise workspace using a REST API. Use this to build
reporting pipelines, trigger workflows in Zapier, or sync ticket data with
external systems.
Pass a JSON object in the filters query parameter to narrow results. The
object has a combinator (always "and") and an array of rules.Each rule specifies a field, an operator, and a value.
The API allows 500 requests per 60-second window per API key. If you exceed
this limit, the API returns 429. Implement exponential backoff or space your
polling intervals accordingly.