---
title: "Every record of one custom type, newest first"
method: GET
path: "/v1/objects/{type}"
tags: ["custom objects"]
---

# Every record of one custom type, newest first

`GET /v1/objects/{type}`

## Request

- Base URL: `https://api.indraft.io`
- URL: `https://api.indraft.io/v1/objects/{type}`
- Auth: HTTP bearer

Records of one custom object type, newest first, with a cursor for the next page. The type must be one this workspace defined; ask get_crm_schema or list_object_types for the names. Filters and sorts exactly like the built-in lists, on the fields the type declared indexed.

## Path parameters

- `type` string, required

## Query parameters

- `limit` integer: How many to return. The page bound is published in the schema call, and asking for more is refused rather than quietly truncated.
- `cursor` string: The opaque marker from the previous page. Store it and hand it back; do not parse it. A cursor is only ever emitted when another row really exists, so a page you were given is never empty.
- `updatedSince` string: Only rows changed after this instant. The incremental read: without it a service syncing a large workspace has to walk all of it every time.
- `lastInteractionBefore` string: Only records whose most recent interaction is older than this, including those with none at all.
- `includeArchived` boolean: Include archived rows. Off by default, because a list is what you are working on and history is somewhere you go deliberately.
- `filter` union: Predicates, all of which must hold, written field:op:value. Only fields an index serves are accepted, and asking for one that is not names the ones that are.
  - string
  - string[]
- `or` union: Alternatives, ORed with each other and ANDed with filter. One level and never a tree: owned by me or owned by nobody is the question people ask, and anything deeper has a cost the caller cannot read off it.
  - string
  - string[]
- `sort` string: A field to order by, with a leading minus for descending. Indexed fields only, for the same reason as filter.

## Response `200`

Success

- object
  - `items` object[], required
    - `id` string, required
    - `version` integer, required
    - `createdAt` string, required
    - `updatedAt` string, required
    - `archivedAt` string, required
    - `values` object, required
    - `links` object, required
    - `lastActor` object
      - `id` string, required
      - `kind` 'human' | 'agent' | 'api_token' | 'system', required
      - `label` string, required
    - `stage` object
      - `pipelineId` string, required
      - `stageId` string, required
      - `status` 'open' | 'won' | 'lost', required
  - `nextCursor` string, required
  - `requestId` string, required

## Other responses

- `401`: No credential, or one that has been revoked.
- `403`: Authenticated, and this capability is not held.
- `404`: No such record, or it belongs to another workspace.
- `422`: The request does not satisfy the schema on this page.
- `429`: Infrastructure protection tripped. This is not a product quota.
- `500`: A defect on our side. The hint says so, and carries an incident id.

---

[API](https://skmtc.dev/indraft/apis/indraft-api.md) · [All operations](https://skmtc.dev/indraft/apis/indraft-api/llms.txt) · [OpenAPI document](https://skmtc.dev/indraft/apis/indraft-api/revisions/d9bb05346d66?raw)