---
title: "Look up member by identifier"
method: POST
path: "/api/v1/members/lookup"
tags: ["API v1"]
---

# Look up member by identifier

`POST /api/v1/members/lookup`

Look up a member by one of the supported identifier combinations:

- subscriber_id only: exact match on subscriber ID
- phone_number only: matches primary or alternate phone (digit-normalized)
- subscriber_id + date_of_birth: both must match the same record

Returns basic member information including support team and language.

Requires scope: members:read

Note: Uses POST to keep PHI out of URLs (compliance requirement).

## Request body

- MemberLookupRequest — Request schema for unified member lookup endpoint. Valid combinations: - subscriber_id only - phone_number only - subscriber_id + date_of_birth (both must match the same record)
  - `subscriber_id` string, nullable
  - `phone_number` string, nullable
  - `date_of_birth` string, date, nullable

## Response `200`

OK

- MemberLookupResponse — Response schema for member lookup endpoint.
  - `lookup_status` string, nullable
  - `subscriber_id` string, nullable
  - `first_name` string, nullable
  - `last_name` string, nullable
  - `master_record_id` string, nullable
  - `support_team` string, nullable
  - `language_code` string, nullable

## Other responses

- `404` — Not Found

---

[API](https://skmtc.net/cloverhealth/apis/clover-api.md) · [All operations](https://skmtc.net/cloverhealth/apis/clover-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cloverhealth/clover-api/revisions/28797307aae6/schema)