# Accounts v1 support for new Connect integrations

Learn when you might need to use the Accounts v1 API and how to enable it.

When building a new Stripe integration, use the Accounts v2 API (`/v2/core/accounts`) unless you’re explicitly instructed to use Accounts v1. If an error directed you to this page, make sure that you’re using `/v2/core/accounts` to create Accounts.

## Use the Accounts v2 API for Connect

Stripe recommends the [Accounts v2 API](https://docs.stripe.com/connect/accounts-v2.md) (`/v2/core/accounts`) for most Connect integrations. It uses *configurations* (Account configurations represent role-based functionality that you can enable for accounts, such as merchant, customer, or recipient) to support multiple types of relationships that connected accounts have with your platform, and is interoperable with most v1 APIs. When using the Accounts v1 API, additional relationships require you to create additional objects representing your connected accounts.

For best practices, see [Configure the behavior of connected accounts](https://docs.stripe.com/connect/accounts-v2/connected-account-configuration.md).

## Use v1 endpoints with v2 Accounts

The Accounts v1 support policy only controls whether your platform can create `Accounts` with `POST /v1/accounts`. When you disable it, you can continue to use other v1 endpoints with v2 `Accounts`, such as `/v1/accounts/{id}/external_accounts`. Your v2 `Accounts` also continue to send v1 events, such as `account.updated`. For details, see [Use v2 Accounts in v1 endpoints](https://docs.stripe.com/connect/accounts-v2/migrate-integration.md#use-v2-accounts-in-v1-endpoints).
