# API v1.0 is deprecated

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

The provider has made API v1.0 obsolete and deprecated it without a specific shutdown date, scheduling its removal for 2026 release wave 1. The retirement affects calls to /v2.0/{}/api/v1.0/*. Once removed, these requests will fail.

## What to use instead

Call API v2.0 instead by using /api/v2.0/ in the same URL. The transition requires more than updating the path, as developers must follow Microsoft's Transitioning from API v1.0 to API v2.0 guide to handle 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/{}/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-2/

## 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