---
title: "Export tickets as JSON"
url: https://docs.gleap.ai/en/reference/rest-api/export-tickets
method: GET
path: "/tickets/export"
api: "API Reference"
tag: "Ticket"
operationId: "ExportTickets"
updatedAt: "2026-11-01T18:40:15.677Z"
language: en
---

# Export tickets as JSON

`GET https://api.gleap.io/v3/tickets/export`

Returns the project's tickets as a JSON array, capped at 25,000 tickets. Supports the usual ticket filters. For larger exports or CSV output use GET /tickets/csv-export.

Unlike GET /tickets, exports include archived tickets by default — there is no `ignoreArchived` to set (it is accepted and ignored). Narrow the export with `archived=true` / `archived=false` instead.

This endpoint returns ticket records only, not their conversations: fetch each ticket's messages with GET /messages?ticket={ticketId}. Retention limits which conversations still exist — see GET /tickets.

`type` accepts one ticket type (default `BUG`) or a comma-separated list (`BUG,INQUIRY,BOT`) to export several boards — `BOT` is the Kai conversations lane — in one file; the `type` field tells rows apart.

`startDate`/`endDate` (ISO 8601, inclusive) filter on `createdAt`; filter on the update time with `updatedAt>=…&updatedAt<=…` (UTC, `Z` suffix). `sort`, `skip` and `limit` are ignored, so this endpoint cannot page past 25,000 tickets.

## Authorization

- `Authorization` (header, required): `Bearer <token>`

## Headers

- `project` (string, required)

## Example request

```bash
curl --request GET \
  --url https://api.gleap.io/v3/tickets/export \
  --header 'Authorization: Bearer <token>' \
  --header 'project: <project>'
```

## Responses

### 200 (`application/json`)

Ok
