> For the complete documentation index, see [llms.txt](/llms.txt)

# API v3 to v3.6 migration guide

## Start here

The following short guide is for customers migrating from API v3 to API v3.6 and supplements our [API reference documentation](/api/latest/). If you're migrating from API v2 to API v3.6, you should refer to our separate [API v2->v3.6 migration guide](/api/api-v2-to-v3-migration-guide/) instead. For a list of the new features in API v3.6, please refer to our [API release notes](/api/release-notes/).

If you have any difficulties migrating, please contact Entrust's [Customer Support team](mailto:identity-support@entrust.com).

## Summary of differences

### Base URL

The base URL for the [European region](/api/latest/#regions) has changed to `api.eu.onfido.com` from API v3.1 onwards.

If you're deployed in the [European region](/api/latest/#regions) using `api.onfido.com` with API v3, you should use the new base URL `api.eu.onfido.com` with API v3.6.

You can read more about our [supported regions](/api/latest/#regions).

### Applicant consent

From API v3.4 onwards, there is new applicant data required when creating identity verification flows.

#### Location

From API v3.4 onwards, Entrust has introduced a new `location` parameter in the [applicant](/api/latest/#applicants) and [documents](/api/latest/#documents) resources for specifying the location of an applicant.

**The `location` parameter is mandatory for all applicants in order to create identity verification flows from API v3.4 onwards.** If you do not provide it, all verification requests will fail with a [validation error](/api/latest/#error-codes-and-what-to-do).

#### Consent

Entrust has introduced a new `consents` parameter in the [applicant resource](/api/latest/#applicants).

**The `consents` parameter is mandatory for any applicant who is located in the US in order to create identity verification flows from API v3.4 onwards.** If you do not provide the consents parameter, and the location of the applicant is the US, all verification requests will fail with a [validation error](/api/latest/#error-codes-and-what-to-do).

For customers who have not migrated to [Workflow Studio](/getting-started/classic-to-studio-migration/) and are creating identity verification flows using our checks API endpoint, the `privacy_notices_read_consent_given` parameter no longer exists in check creation.

You can read our [Privacy notices and consent migration guide](/guide/migration-guide-onfido-privacy-notices-and-consent/) for further guidance on how to update your integration to collect end user consent in API 3.6.

### Versioning policy

Our versioning policy has changed from v3.6 onwards, you can read about in [our versioning policy page](/api/api-versioning-policy/).