How to migrate OData to API Pages in Dynamics 365 Business Central
You have probably already heard the announcement that Microsoft is gradually deprecating the ability to expose UI pages as OData (and SOAP) endpoints. Instead, you will need to use API Pages. This deprecation is part of a multi-year modernization strategy to standardize integrations around API pages and Query APIs, which are purpose-built for programmatic access.
Quick answer: Migrating OData to API pages in Dynamics 365 Business Central involves identifying the OData endpoints, creating corresponding API pages, and transferring your data while ensuring proper permissions and data consistency. This process enables faster, more secure, and modernized data access.
Key Migration Dates and Changes
- 2025 (v26, Wave 1): Warnings appear if you use OData with UI pages.
- 2026 (v28 to v29): Microsoft adds new API features and more warnings.
- 2027 (v30, Wave 1): OData with UI pages stops working. Only API Pages and API Queries will work.
Source: Microsoft Deprecated Features in Business Central
It might seem somewhat early, but the sooner you are prepared, the better you will be positioned when you need to switch.
Why Microsoft Is Moving Away from OData
- API Pages are for integrations. UI pages are for people.
- API Pages handle data faster and work better with filters and large amounts of data.
- API Pages have better controls for who can access what.
- API Pages use version numbers, so updates are less likely to break your integrations.
OData vs API Pages: What's Different?
| Feature | OData (UI page) | API page |
|---|---|---|
| What it does | Shares UI page as endpoint | Built for integrations |
| Speed | Slower with lots of data | Faster, handles more records |
| Versioning | None | Yes (v2.0, v3.0, etc.) |
| Stability | Changes if UI changes | More stable, contract-based |
| Security | Based on page | Based on data contract |
| Support | Going away | Fully supported |
API Pages vs API Queries: Which Should You Use?
API Pages and API Queries both give you access to data in Business Central, but they have different uses:
- API Pages: Use these for working with records in a table (like customers or sales orders). You can read, create, update, and delete records if you have permission.
- API Queries: Use these when you need to pull data from more than one table or need a custom report. API Queries can join, filter, and group data, but they are read-only. They're good for custom reports or summary data.
In short: Use API Pages for standard data tasks. Use API Queries for custom reports or when you need to combine data from different places.
How to Migrate from OData to API Pages: Step by Step
- Change old OData endpoints like
/ODataV4/Page/CustomerCardto API Page endpoints like/api/v2.0/customers,/vendors, or/salesOrders. - Update your integration mappings and refresh metadata.
- Use fields like
systemModifiedAtorlastModifiedDateTimefor syncing only changed data. - Test your integrations in a safe environment. API Pages usually work 30 to 50% faster.
- If you need custom fields, build custom API Pages with AL extensions.
Read more in this article about how to read and integrate with Microsoft Dynamics 365 Business Central API pages.
💡 Pro tip: Switching soon keeps your integrations working and makes maintenance easier.
As always, if you need help switching your Business Central integration from OData to API Pages, please reach out to the Rapidi Support Team for assistance.
Frequently Asked Questions
When do OData endpoints stop working?
OData UI page endpoints stop working in version 30 (2027 Wave 1).
Why use API Pages instead of OData?
API Pages are faster, more secure, and less likely to break.
Do I need to rewrite all integrations?
If your integration uses OData UI pages, you need to switch to API Pages or API Queries before 2027.
Last updated: 12 November 2026
Need Help Moving to API Pages?
Tell us how your integration reads Business Central today, and we will say plainly what has to change.