# API v1.0 is deprecated

Business Central API deprecated /v2.0/{}/sandbox/api/v1.0/* without giving a shutdown date yet.

The provider deprecated API v1.0 on April 1, 2024, without a shutdown date, though it will be removed in 2026 release wave 1. The retirement hits requests to /v2.0/{}/sandbox/api/v1.0/* endpoints. After removal, these calls will fail.

## What to use instead

Call API v2.0 instead by replacing the path with /api/v2.0/ in the same URL. Following the transition involves more than changing the endpoint, as you must adjust for renamed fields and SystemId keys.

- API: Business Central API (api.businesscentral.dynamics.com)
- Kind: Version retirement
- Announced: April 1, 2024
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/v2.0/{}/sandbox/api/v1.0/*`
- Source: [Announcement](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/deprecated-features-w1)
- Verified: October 26, 2026, against Business Central API's own pages
- Page: https://www.okapi.bot/providers/business-central-api/breaking-changes/api-v1-0-is-deprecated-4/

## Business Central API's words

> We're making the API (v1.0) obsolete in 2024 release wave 1 (to be removed in 2026 release wave 1). The API (v1.0) will be removed in 2026 release wave 1.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent