Skip to main content
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.
You need an API key. Create one in Workspace Settings → API Keys.

Endpoint

Authentication: Pass your API key as a Bearer token.

Quick start

cURL

Query parameters

number
default:"0"
Zero-based page index for pagination.
number
default:"20"
Number of tickets to return per page.
string
default:"updatedAt"
Field to sort by. Supported values include createdAt, updatedAt, and humanAgentRating.
string
default:"desc"
Sort order. Use asc for ascending or desc for descending.
string
Free-text search across ticket title, summary, and customer name.
string
URL-encoded JSON object that combines one or more filter rules. See Filters below.

Filters

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.

Filter fields

For humanAgentRating, use the sentinel value "no_assignee" to match conversations that have not been rated by an agent or admin yet. You can combine it with numeric scores in the same in rule.

Example filter

This filter returns open tickets with a CSAT rating of 4 or 5, created in Q1 2026:

Response

number
required
Total number of tickets matching the query across all pages.
Ticket[]
required
Array of ticket objects for the current page.

Code examples


Errors


Rate limiting

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.

See also