> For the complete documentation index, see [llms.txt](https://support.iafcertsearch.org/verifiers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.iafcertsearch.org/verifiers/release-notes/release-announcements/release-notes-may-29-2026.md).

# \[Release Notes] May 29, 2026

#### **Sharper Matching in the API**

Matching used to rely almost entirely on the company name. It now weighs several pieces of information together, so you find the right company more often and can see how confident the result is.

**What's New:**

* **Country and city as scoring signals**, alongside the company name.
* **Company identifiers in scoring.** An exact identifier returns a single definitive match.
* **Multiple results returned**, so you can review the alternatives instead of accepting one answer.
* **Set your own match threshold** and receive only results at or above it.
* **Exact matches now score 100** when name, country, and city all agree.<br>

To know more about this feature, go to: [Verification Users API Developer Guide](https://support.iafcertsearch.org/verification-users-api-developer-guide/api-integration/verification-apis)

## Frequently asked questions

<details>

<summary>What happens if I do not set a match threshold?</summary>

A default 94 threshold applies. If you want tighter or looser results, set the threshold explicitly on your request.

</details>

<details>

<summary>What if the identifier I send is wrong?</summary>

You now receive a usable response rather than an error, so an incorrect identifier no longer breaks the request.

</details>

<details>

<summary>Do I need to send country and city?</summary>

`company_country` is mandatory on every request. `company_city` is optional, but supplying it raises the score for companies in that city, so include it wherever you have it. Beyond those two, the more signals you provide, the more confident the match.

</details>