Visual Studio App Center CodePush management API removal

Stopped workingMarch 31, 2025Subscribe to Visual Studio App Center APIShare

On March 31, 2025, the CodePush management service was retired alongside other App Center features. Requests targeting /v0.1/apps/{id}/{id}/deployments* fail after that day. Any systems relying on these management endpoints to deliver updates can no longer access them.

Calls it hits

/v0.1/apps/{id}/{id}/deployments*

What to use instead of these calls

Host the standalone CodePush Server or adopt an alternative over-the-air update service, then point your requests to the replacement endpoint. Because Microsoft provides only a self-hosted CodePush Server, your team must decide whether to operate that server independently or migrate to a different service.

Microsoft offers only a self-hosted CodePush Server: the team hosts it or picks another OTA update service.

In Visual Studio App Center API's words

CodePush, along with other App Center features, was also retired on March 31, 2025.

Visual Studio App Center API, Announcement

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: October 25, 2026
Verified: November 6, 2026, against Visual Studio App Center API's own pages

Questions

When does this change take effect?

Calls to /v0.1/apps/{id}/{id}/deployments* 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.

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub