> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voxmind.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> A record of all notable changes to the Voxmind API and developer platform — new features, improvements, deprecations, and breaking changes.

This changelog follows [Semantic Versioning](https://semver.org/) for the API. Breaking changes increment the major version and are always communicated with a minimum 60-day deprecation notice. Non-breaking additions and improvements increment the minor version. Bug fixes increment the patch version.

To receive change notifications by email, enable changelog alerts in your [account settings](https://developers.voxmind.ai/settings/notifications).

***

## v1.1.0 — 2025-03-01

**Deepfake detection now included on all verification calls.**

AASIST-based deepfake detection is now enabled by default across all plans and all verification calls. The `deepfake_detected` field in webhook results and verification responses reflects the result of this check. No integration changes are required to receive the signal — if you are already handling webhook results, `deepfake_detected` will now always be present in the payload.

We recommend auditing your webhook handler to ensure you are evaluating `deepfake_detected` before your match score threshold logic. See the [Deepfake Detection guide](/guides/deepfake-detection) for the correct decision tree and application logic patterns.

***

## v1.0.0 — 2024-12-02

**General Availability.**

Voxmind API v1.0.0 is generally available. The v1 API surface is stable — breaking changes will be communicated with a minimum 60-day deprecation period and will increment the major version number.

The v1 GA release includes: voice enrollment and verification (text-independent, language-agnostic), asynchronous webhook delivery, API token management, user and organisation management, and the Billing API for plan and subscription retrieval.

***

## Deprecation policy

When a feature, endpoint, or behaviour is deprecated, it will continue to function for a minimum of 60 days after the deprecation announcement. Deprecation notices appear in this changelog under a **Deprecated** heading and are also sent by email to the technical contact on your account. After the deprecation window closes, the feature is removed in the next major version release.

## Breaking change history

No breaking changes have been introduced since v1.0.0 GA.