# For legacy app developers

Legacy integrations were built on API v2, which has now been **deprecated.** As of **November 1, 2025,** API v2 and all legacy integrations no longer have access to Ahrefs data.

As a replacement, we’ve launched **Ahrefs Connect** — a similar integration program based on our current API v3. Legacy developers were informed about this transition in advance via email.

See [How it works](./how-it-works.md) for an overview of the new program.

## **What this means for you**

- If your app was previously **active** in the legacy Integrations program, it has been automatically included in Ahrefs Connect.
- Legacy developers do **not** need to purchase an Enterprise subscription to activate their app in the new system — unlike new partners, who are required to have one.
- You should already see an **Ahrefs Connect** section in your Account settings, where you can continue development using API v3.

![](<../images/Account settings legacy.jpg>)

## **Migration steps**

1. **Implement the new OAuth flow**: see [OAuth guide](./oauth-guide.md). The new flow uses Authorization Code with Proof Key for Code Exchange (PKCE).
2. **Update API calls to v3 endpoints**: see [API guide](./api-guide.md). API v3 offers more data points than v2, but some specific fields may differ. If something you use is missing, contact [support@ahrefs.com](mailto:support@ahrefs.com) to discuss alternatives.
3. **Submit for approval**: follow the [Approval process](./approval-process.md).

Read more about the [Ahrefs Connect program](./introduction.md) and the [API v3 documentation](https://docs.ahrefs.com/docs/api/reference/introduction).