Visual Studio App Center Build API removal
Stopped workingSubscribe to Visual Studio App Center APIShare
Calls to /v0.1/apps/{id}/{id}/builds* on Visual Studio App Center API stopped working on March 31, 2025.
Calls it hits
/v0.1/apps/{id}/{id}/builds*
What to use instead of these calls
App Center Build has no direct API successor, requiring teams to select another CI service. Move your builds to Azure Pipelines using Export App Center Build or adopt another CI platform, then update your integrations to call that service's API instead.
App Center Build has no API successor: the team picks another CI service.
In Visual Studio App Center API's words
Visual Studio App Center is scheduled for retirement on March 31, 2025 . After that date, it will not be possible to sign in with your user account nor make API calls.
Facts
- API
- Visual Studio App Center API
api.appcenter.ms - Kind
- Removal
- Takes effect
- March 31, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Visual Studio App Center API's own pages
Questions
When does this change take effect?
Calls to /v0.1/apps/{id}/{id}/builds* on Visual Studio App Center API stopped working on March 31, 2025.
What happens to calls after March 31, 2025?
They have failed since March 31, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Visual Studio App Center API 3
-
/v0.1/apps/{id}/{id}/branches*Removal Stopped working -
/v0.1/apps/{id}/{id}/deployments*Removal Stopped working -
/v0.1/apps/{id}/{id}/test_runs*Removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.