---
title: "Name Match Verification"
method: POST
path: "/verify/name_match"
tags: ["Name Match"]
---

# Name Match Verification

`POST /verify/name_match`

Matches two names for similarity. Accepts JSON with `name_1` and `name_2`. Requires `X-API-KEY` and `X-Client-ID` headers.

## Request body

- NameMatchRequest
  - `user_id` string — Optional caller-supplied reference for the end user
  - `name_1` string, required — First name to compare
  - `name_2` string, required — Second name to compare

## Response `200`

Successful name comparison

- NameMatchResponse
  - `name_1` string, required — First name as supplied in the request
  - `name_2` string, required — Second name as supplied in the request
  - `match_score` number, float, required — Similarity score from 0 to 100
  - `match_status` boolean, required — True when match_score is at or above the match threshold (80)
  - `status` string, required — Operation status (e.g., success)
  - `chargeble` string — Billing flag, present on success (string for backward compatibility)
  - `user_consent` string — Consent flag, present on success (string for backward compatibility)

## Other responses

- `400` — Bad request — missing or invalid names.
- `401` — Unauthorized - Invalid or missing API key or client ID
- `500` — Internal server error.

---

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