[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# List tickets

> Tickets you may see, filtered by mode, category, status, priority, tag, company or date. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/jitbit/list_tickets

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Tickets you may see, filtered by mode, category, status, priority, tag, company or date.

Jitbit API: https://cotlet.dev/docs/api/jitbit.md

`GET https://cotlet.dev/api/v1/jitbit/tickets`

Access: read.

Returns tickets with status, priority, category, submitter, company, assigned technician and last update, without comments. mode matches the tabs of the Tickets page: unanswered, unclosed, unassigned, handledbyme or all. Only tickets your Jitbit user may see are returned: a technician sees the categories they handle and an administrator sees everything. Use offset to read the next page and get_ticket for the full thread.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `mode` | enum | no | unanswered, unclosed, unassigned, handledbyme or all. Default: all. |
| `category` | string | no | Category name, as in the left menu of the Tickets page. |
| `status` | string | no | Status name, for example New, In process, Resolved or one of your custom statuses. |
| `priority` | string | no | Priority name, for example Low, Normal, High, Critical or a custom one. |
| `tag` | string | no | Only tickets with this tag. |
| `company` | string | no | Only tickets from this company. |
| `updated_before` | string | no | ISO date, for example 2026-10-08. Only tickets last updated before it. |
| `updated_after` | string | no | ISO date. Only tickets last updated after it. |
| `limit` | integer | no | How many to return. Default: 25. |
| `offset` | integer | no | How many to skip, for the next page. Default: 0. |

## Request

**cURL**

```bash
curl https://cotlet.dev/api/v1/jitbit/tickets \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

**Python**

```python
result = client.call("jitbit", "list_tickets")
```

**Node.js**

```js
const result = await cotlet.call('jitbit', 'list_tickets');
```

**CLI**

```bash
cotlet call jitbit list_tickets
```

## Example response

```json
{
  "tickets": [
    {
      "ticket_id": 5128,
      "subject": "Cannot log in after password reset",
      "status": "New",
      "priority": "Normal",
      "category": "Technical support",
      "submitter": "Maya Brandt",
      "company": "Brandt Studio",
      "assigned_to": null,
      "created_at": "2026-10-22T06:41:00Z",
      "last_updated": "2026-10-22T06:41:00Z",
      "last_updated_by": "customer"
    }
  ],
  "offset": 0
}
```

Next: [Search tickets](https://cotlet.dev/docs/api/jitbit/search_tickets.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.