---
title: "List Clients"
method: GET
path: "/api/autopilot/clients"
tags: ["autopilot"]
---

# List Clients

`GET /api/autopilot/clients`

## Request

- Base URL: `https://api.taxcompass.it` (the document declares no server; this is the origin it was published from)
- URL: `https://api.taxcompass.it/api/autopilot/clients`
- Auth: HTTP bearer

The caller's customer address book, newest first.

An empty list rather than a 204: unlike the profile, "no clients yet" is a
normal steady state the picker renders as an empty list, not a missing
resource.

## Response `200`

Successful Response

- ClientRead[]
  - `display_label` string, required
  - `country` string
  - `is_business` boolean
  - `codice_destinatario` string, nullable
  - `denomination` string, nullable
  - `given_name` string, nullable
  - `family_name` string, nullable
  - `partita_iva` string, nullable
  - `codice_fiscale` string, nullable
  - `pec` string, nullable
  - `street` string, nullable
  - `cap` string, nullable
  - `comune` string, nullable
  - `provincia` string, nullable
  - `id` string, uuid, required
  - `created_at` string, date-time, nullable
  - `verified` boolean, nullable
  - `verify_detail` ClientVerification: What the registry answered about one client's identifier, if it was asked. Metadata only. The identifier itself is identity — it lives in the encrypted ``details`` envelope — so it is deliberately absent here and from the column this mirrors: a verification record must not become a second, plaintext copy of the customer's partita IVA.
    - `provider` string, required
    - `kind` 'piva' | 'cf', required
    - `status` 'found' | 'not_found' | 'unreachable', required
    - `checked_at` string, date-time, required
    - `reason` string, nullable

---

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