---
title: Cases
url: https://www.tines.com/stories/docs/api/records/cases/
updated: 2026-09-23T08:49:50+00:00
description: List the cases linked to the given record, oldest case first (ordered by case ID, not by when the case was linked). Results are keyset-paginated.
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/stories/docs/llms.txt) › [Tines API](https://www.tines.com/stories/docs/api/llms.txt) › [Records](https://www.tines.com/llm/stories/docs/api/records.md)*

# Cases

*[View on tines.com](https://www.tines.com/stories/docs/api/records/cases/)*

## Description

List the cases linked to the given record, oldest case first (ordered by case ID, not by when the case was linked). Results are keyset-paginated.

This is the paged equivalent of the `cases` embed on the [Get record API](/api/records/get): the embed is capped at 20, whereas this endpoint pages through the full set visible to the caller. See the [Cases API](/api/cases/get) to read a case in full.

## Request

HTTP Method: **GET**

| Path parameter | Description           |
| -------------- | --------------------- |
| id             | The ID of the record. |

| Query parameter | Description                                                                                      |
| --------------- | ------------------------------------------------------------------------------------------------ |
| timezone        | **Optional** IANA timezone name for timestamp output. Defaults to UTC.                           |
| limit           | **Optional** Page size, between 1 and 500. Defaults to 20.                                       |
| after           | **Optional** Opaque forward pagination cursor from a previous response's `page.next_page_token`. |

```bash
curl -X GET \
  https://<tenant-domain>/api/v2/records/<<record_id>>/cases \
  -H 'content-type: application/json' \
  -H 'Authorization: Bearer <<CREDENTIAL.tines_api_key>>'
```

### Pagination

When more results exist, the response's `page` object contains a `next_page_token`; pass it back as the `after` query parameter to fetch the next page. On the last page, `page` has no `next_page_token`.

## Response

A successful request returns a JSON object with a `data` array of linked cases and a `page` pagination cursor.

### Field description

Each object in `data` contains:

| Field      | Description                                                                                                             |
| ---------- | ----------------------------------------------------------------------------------------------------------------------- |
| id         | The public case number (for example `42`) — the identifier used to address the case in the [Cases API](/api/cases/get). |
| name       | The case name.                                                                                                          |
| status     | The case status.                                                                                                        |
| priority   | The case priority (severity).                                                                                           |
| linked_at  | ISO 8601 timestamp of when the case was linked to this record.                                                          |
| created_at | ISO 8601 case creation timestamp.                                                                                       |
| updated_at | ISO 8601 case last-updated timestamp.                                                                                   |

The `page` object contains a `next_page_token` when another page exists.

### Sample response

```json
{
  "data": [
    {
      "id": 42,
      "name": "Investigation",
      "status": "open",
      "priority": "high",
      "linked_at": "2026-07-05T09:00:00Z",
      "created_at": "2026-07-03T00:00:00Z",
      "updated_at": "2026-07-03T00:00:00Z"
    }
  ],
  "page": {}
}
```

## Errors

| Status | Meaning                                                                                |
| ------ | -------------------------------------------------------------------------------------- |
| 400    | Invalid request — unknown query parameter, invalid timezone, limit, or `after` cursor. |
| 403    | The tenant does not have access to records.                                            |
| 404    | Record not found.                                                                      |

Errors are returned as `{ "error": { "type", "message", "field"?, "hint"? } }`.