Export history API endpoint deprecated
Export history API endpoint deprecated
The admin center API export history endpoint is deprecated and kept only on API versions 2.29 and earlier. Automations should move to the environment operations API.
Area: Admin and platform. Status: GA. Developer relevance: medium. Airtime: 1 min across 1 video.
Status evidence
- Nothing said about status; launch event convention: generally available unless stated otherwise.
Where they talk about it
- What's new: Database Export Enhancements: 3:15 to 4:03 (called "Export history endpoint deprecated in admin center API" there)
Quotes
- 3:15 "if you automate against the admin center API, the expert history endpoint is deprecated." - Flags a breaking change for anyone with automation against the admin center API.
- 3:28 "It keeps working on API versions 2.29 and earlier, but it is not carried forward to newer versions." - Gives the exact API version limit for the deprecated endpoint.
- 3:40 "you should move them to use the environment operations API." - States the migration path for automations.
Caveats mentioned
- Works only on API versions 2.29 and earlier
- Not carried forward to newer API versions
Prerequisites mentioned
- Existing automations against the admin center API need migrating to the environment operations API
Documented features match
- No documented item matched. Not documented
- Product documentation: Business Central Admin Center API - Environment database export, checked 2026-10-02. The API endpoint to get export history is supported up until version 2.29 of the API, and is deprecated from version 2.30. Note: Points to Environment Operations endpoints instead.
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale.
Tags: api, admin, deprecation, automation
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.