---
title: "List Models"
method: GET
path: "/api/models"
tags: ["Models"]
---

# List Models

`GET /api/models`

Lists all models in the caller's organization.

Results are ordered by `updated_at` descending, with `id` used as a tiebreaker.
If more results are available, the response includes `pagination.next_page_token`.
Pass that token back unchanged to continue from the last item you received.

The token is opaque. Do not construct or edit it yourself.

The `limit` is capped at 50. Values above that cap are reduced to 50, and
non-positive values fall back to the same default.

## Headers

- `X-Polytomic-Version` string

## Response `200`

OK

- ModelListResponseEnvelope
  - `data` ModelResponse[], nullable
    - `configuration` object
    - `connection_id` string, uuid
    - `created_at` string, date-time
    - `created_by` OutputActor
      - `id` string, uuid
      - `name` string
      - `type` string
    - `enricher` Enrichment
      - `configuration` EnricherConfiguration — Similar to a model configuration, this configures the enricher. For example, if you wanted to use Apollo to enrich people, you would send `{"object": "people"}` as the configuration. Each enricher configuration can be found in the connection configuration docs.
      - `connection_id` string, uuid
      - `enricher_id` string, uuid — Must be provided to update an existing enrichment
      - `fields` ModelField[] — If not provided, all fields will be enabled.
        - `created_at` string, date-time
        - `created_by` OutputActor
          - `id` string, uuid
          - `name` string
          - `type` string
        - `description` string
        - `example` unknown
        - `id` string, uuid
        - `label` string
        - `name` string
        - `remote_type` string
        - `type` string
        - `unique` boolean
        - `updated_at` string, date-time
        - `user_added` boolean
      - `mappings` EnricherMapping — A map of parent model Source Name to child model Source Name. For example, if your model has a field called `work_email` and the enricher accepts a field called `email`, you'd send a map of `{"work_email":"email"}`. The set of required input mappings varies based on the configuration of the enrichment. You can use the `enrichment/{connection_id}/inputfields` API to discover available input field combinations for a given configuration.
    - `fields` ModelField[]
      - `created_at` string, date-time
      - `created_by` OutputActor
        - `id` string, uuid
        - `name` string
        - `type` string
      - `description` string
      - `example` unknown
      - `id` string, uuid
      - `label` string
      - `name` string
      - `remote_type` string
      - `type` string
      - `unique` boolean
      - `updated_at` string, date-time
      - `user_added` boolean
    - `id` string, uuid
    - `identifier` string
    - `labels` LabelLabel[]
    - `name` string
    - `organization_id` string, uuid
    - `policies` string[]
    - `relations` Relation[]
      - `from` string
      - `to` RelationTo
        - `field` string
        - `model_id` string, uuid
    - `tracking_columns` string[]
    - `type` string
    - `updated_at` string, date-time
    - `updated_by` OutputActor
      - `id` string, uuid
      - `name` string
      - `type` string
    - `version` integer

## Other responses

- `404` — Not Found

---

[API](https://skmtc.net/polytomic/apis/polytomic-api.md) · [All operations](https://skmtc.net/polytomic/apis/polytomic-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/polytomic/polytomic-api/versions/5e9bcd4cfb2d/schema)