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

# \[Release Notes] July 8, 2026

**Faster API Responses**

The API now spends less time getting ready and more time answering. We have reworked how the backend handles incoming requests so it no longer rebuilds itself from scratch on every call, which takes a slice of delay off each one.

**What's New:**

* **Quicker responses across the matching and verification endpoints**, on every request rather than only the first.
* **The biggest gains on high volume work.** Because the saving applies to each individual call, it adds up considerably across a large bulk run.
* **Same results, same credits.** Matching, scoring, and credit consumption are untouched.

Nothing changes on your side. Endpoints, request formats, response formats, and business logic are all exactly as they were, so no action is needed.

[See the Verification APIs reference](https://support.iafcertsearch.org/verification-users-api-developer-guide/api-integration/verification-apis)

## Frequently asked questions

<details>

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

No. This release changes nothing about the endpoints, the fields you send, or the fields you receive. No action is required.

</details>

<details>

<summary>Will my results change?</summary>

No. Matching, scoring, and credit behaviour are all unaffected. Only the speed of the response changes.

</details>