`GET /associated_persons/{id}`

Fetch by id, no customer id required.

curl "$BASE_URL/associated_persons/ap_01HZ…" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY"

Response (200)

{
  "id": "ap_01HZ…",
  "customer_id": "cust_01HZ…",
  "first_name": "Alice",
  "last_name": "Zhang",
  "email": "alice@example.com",
  "birth_date": "1990-04-01",
  "has_ownership": true,
  "has_control": true,
  "is_signer": true,
  "is_director": false,
  "title": "CEO",
  "ownership_percentage": 60,
  "status": "approved",
  "residential_address": {
    "street_line_1": "1 Market St",
    "city": "San Francisco",
    "subdivision": "US-CA",
    "postal_code": "94105",
    "country": "USA"
  },
  "created_at": "2026-04-24T12:00:00Z",
  "updated_at": "2026-04-24T12:00:00Z"
}

status mirrors the parent customer's capability states: pending, under_review, approved, rejected. All other fields are from the AssociatedPerson schema.

Alias

GET /customers/{customer-id}/associated_persons/{id} resolves identically. The extra {customer-id} in the path just adds a scoping check (returns 404 if it doesn't match the person's customer_id).