---
title: "GET /v1/customer/{id}"
method: GET
path: "/v1/customer/{id}"
tags: ["Customer"]
---

# GET /v1/customer/{id}

`GET /v1/customer/{id}`

## Path parameters

- `id` string, uuid, required

## Response `200`

Customer found

- CustomerResponseDTO
  - `firstName` string — The first name of the customer
  - `lastName` string — The last name of the customer
  - `email` string, email — The email of the customer
  - `phoneNumber` string — The phone number of the customer (in international / E.164 format)
  - `displayName` string — The display name of the customer
  - `remoteId` string — The id of the customer in the ticketing system. For the SDK this needs to be stable and unique
  - `subscriberCustomerId` string — The id of the customer in your own primary database or a unique identifier, for example a cookie
  - `subscriberToken` string — A token that can be used to authenticate the customer in the your system, like a JWT
  - `avatarUrl` string — The URL of the customer avatar
  - `id` string, uuid, required — The id of the customer in the subscriber system
  - `createdAt` string, date-time, required — The timestamp of the when the customer was created in our system

## Changes

- **2026-02-11** `b4f394f05daf` — 1 info
  - the endpoint scheme security `lorikeetClientId AND lorikeetSignatureAuthV1` was removed from the API

[Change history](https://skmtc.dev/optechai/apis/lorikeet-api/changes/v1/customer/:id/get.md)

---

[API](https://skmtc.dev/optechai/apis/lorikeet-api.md) · [All operations](https://skmtc.dev/optechai/apis/lorikeet-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/optechai/lorikeet-api/revisions/ea2fb7d0e99f/schema)