---
title: "Suggest customers to link an associated person to"
method: GET
path: "/v0/customers/{id}/kyc/associated-persons/{person_id}/link-suggestions"
tags: ["Customers"]
---

# Suggest customers to link an associated person to

`GET /v0/customers/{id}/kyc/associated-persons/{person_id}/link-suggestions`

## Request

- Base URL: `https://orchestration.seismic.systems/api`
- URL: `https://orchestration.seismic.systems/api/v0/customers/{id}/kyc/associated-persons/{person_id}/link-suggestions`
- Auth: API key in header `Api-Key`

Individual customers of yours whose identity matches an associated person on the business customer's verification profile — the same human onboarded twice. Send a suggested `customer_id` back on that person to link the two, so one verification covers both.

## Path parameters

- `id` string, uuid, required
- `person_id` string, uuid, required

## Response `200`

Suggested customers, best-matched first.

- LinkSuggestionsResponse
  - `suggestions` LinkSuggestionDto[], required
    - `customer_id` string, uuid, required: Id of the suggested individual customer — the value to send as `customer_id` on the associated person to accept the suggestion.
    - `email` string, nullable
    - `first_name` string, nullable
    - `kyc_status` 'draft' | 'submitted' | 'under_review' | 'action_required' | 'approved' | 'rejected' | 'terminally_rejected' | 'paused' | 'unknown', required
    - `last_name` string, nullable
    - `linked` boolean, required: This customer is the one the person is linked to today.
    - `matched_on` LinkMatchKey[], required: Every detail the two records agree on exactly. Never empty.

## Other responses

- `401`: Missing or invalid API key.
- `404`: Customer or associated person not found.

---

[API](https://skmtc.dev/seismic/apis/seismic-orchestration-api.md) - [All operations](https://skmtc.dev/seismic/apis/seismic-orchestration-api/llms.txt) - [OpenAPI document](https://skmtc.dev/seismic/apis/seismic-orchestration-api/revisions/08ada1f159fa?raw)