> 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-july-9-2026.md).

# \[Release Notes] July 9, 2026

#### **API Bulk Matching Now Returns Multiple Results**

When you send a company to the bulk matching endpoint, you now get back every candidate that meets your match threshold rather than a single best result. This brings `POST /bulk-companies` in line with `POST /match-companies`, so the two return results the same way.

**What's New:**

* **Up to 10 results for each company** in your request, ordered by `match_rate` from highest to lowest.
* **A new `match_result_count` field.** The default is **3**, the minimum is **1**, and the maximum is **10**. Any value above 10 is capped at 10.
* **The count applies to each company**, not to the request as a whole, so a request of 100 companies can return considerably more than 100 results.
* **Consistent behaviour** between the bulk companies and match companies endpoints.<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>Will this change how many credits I use?</summary>

Only results returned as `exactly_matched`, meaning a score of 94 to 100, consume credits and save to your default list. Results scoring 30 to 93 come back as `loosely_matched` for your review and consume nothing. So your credit use rises only where a single company genuinely returns several matches in the 94 to 100 band. We recommend reviewing your expected usage before your next large run.

</details>

<details>

<summary>Do I need to change my integration?</summary>

If your integration expects one result for each company, then yes. The response now carries several matches for a single company input, ordered by score. Check the endpoint reference for the exact response shape before you update your parser.

</details>

<details>

<summary>How do I keep the previous behaviour?</summary>

Set the result count to 1 on your request. You will receive the single highest scoring match for each company, as before.

</details>

<details>

<summary>Does this affect `POST /company`?</summary>

No. That endpoint still returns a single matched Certified Entity for each request.

</details>