App Center Client

Name: App Center Client API
Brand: App Center Client
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey,basic351 EndpointsREST

For Agents

Manage App Center mobile app builds, releases, crash groups, analytics audiences, and codepush deployments so an agent can drive a mobile DevOps pipeline from outside the App Center UI.

Quickstart

Get started with App Center Client in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list crash counts for a mobile app"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with App Center Client API.

Trigger and inspect builds for an app via the build endpoint family

Distribute releases to testers and groups through the distribute endpoints

Inspect crash groups and crash counts to triage stability issues

Run analytics queries on active devices, audiences, and event logs

GET STARTED

Start building with App Center Client API

Explore with Jentic

View OpenAPI Document

Use for: I need to list active device counts for a mobile app, Get the current crash groups for an app, List all releases distributed to a tester group, Trigger a CodePush release for a specific app

Not supported: Does not handle source-code hosting, app-store submission, or in-app purchase processing — use for App Center build, distribute, crash, analytics, and CodePush operations only.

The Microsoft Visual Studio App Center API gives mobile DevOps teams programmatic access to App Center's build, test, distribute, codepush, crash, analytics, and account management surfaces. The 351 endpoints cover app provisioning, release distribution, crash group inspection, audience analytics, in-app event logs, and team membership so end-to-end mobile delivery can run from external tooling. Authentication accepts an X-API-Token header or HTTP basic, and the API is organised around the {owner_name}/{app_name} addressing scheme.

Use Cases

Patterns agents use App Center Client API for, with concrete tasks.

★ Mobile Crash Triage Automation

Detect rising mobile crash rates and route them to engineering automatically by walking /v0.1/apps/{owner}/{app}/analytics/crash_groups and /v0.1/apps/{owner}/{app}/analytics/crash_counts. The agent compares the current 24-hour count to a rolling baseline and opens a Shortcut or Linear story for the on-call engineer when the threshold is breached, removing the manual dashboard sweep.

List crash groups via GET /v0.1/apps/{owner}/{app}/analytics/crash_groups, fetch counts for each, and open a story for any group whose 24-hour count exceeds the rolling average by 50 percent

CodePush Release Orchestration

Push hotfix bundles to live mobile apps without going through app-store review by automating CodePush releases through the codepush endpoint family. The agent pairs the CodePush deployment call with crashfree-percentages monitoring so that if crashfree drops after a release, the agent can roll back automatically — turning CodePush into a safer release channel.

Push a CodePush release through the codepush deployment endpoint, then poll /v0.1/apps/{owner}/{app}/analytics/crashfree_device_percentages and roll back if crashfree drops below 99 percent

Tester Group Distribution

Distribute new releases to specific tester groups by combining the distribute endpoint with /v0.1/apps/{owner}/{app}/analytics/audiences for targeted rollouts. This is the typical pattern when releasing a beta to power-users in one country before a global rollout, and the agent can use the audience metadata endpoints to confirm the target population before pushing.

Look up the target audience via /v0.1/apps/{owner}/{app}/analytics/audiences/{audience_name}, then trigger a distribution to that audience via the distribute endpoint

GDPR Export Automation

Honour data-subject access requests by triggering /v0.1/account/test/export and the related GDPR endpoints to produce per-account exports. The agent assembles the resulting export package, posts it to the requesting user's secure channel, and records the request in an audit log, removing the manual export-and-zip work from the privacy team.

Call POST /v0.1/account/test/export with the account identifier, monitor the export status, and deliver the resulting bundle to the privacy team's secure store

Agent-Driven Mobile DevOps

Let an AI assistant answer mobile DevOps questions like 'is the iOS app crashing more this week?' by exposing App Center analytics through Jentic. The agent searches for the right operation, loads its schema, and executes — never holding the X-API-Token, which carries broad write access across the App Center org.

Search Jentic for 'list crash counts for an app', load the schema for /v0.1/apps/{owner}/{app}/analytics/crash_counts, and execute against the named app

Key Endpoints

351 endpoints — the microsoft visual studio app center api gives mobile devops teams programmatic access to app center's build, test, distribute, codepush, crash, analytics, and account management surfaces.

METHOD

PATH

DESCRIPTION

GET

/v0.1/apps

List apps for the account

GET

/v0.1/apps/{owner_name}/{app_name}

Fetch a specific app

GET

/v0.1/apps/{owner_name}/{app_name}/analytics/crash_groups

List crash groups for an app

GET

/v0.1/apps/{owner_name}/{app_name}/analytics/active_device_counts

Pull active device counts

GET

/v0.1/apps/{owner_name}/{app_name}/analytics/crashfree_device_percentages

Get crashfree percentages

GET

/v0.1/apps/{owner_name}/{app_name}/analytics/audiences

List audience definitions

GET

/v0.1/api_tokens

List API tokens for the account

GET

/v0.1/apps

List apps for the account

GET

/v0.1/apps/{owner_name}/{app_name}

Fetch a specific app

GET

/v0.1/apps/{owner_name}/{app_name}/analytics/crash_groups

List crash groups for an app

GET

/v0.1/apps/{owner_name}/{app_name}/analytics/active_device_counts

Pull active device counts

GET

/v0.1/apps/{owner_name}/{app_name}/analytics/crashfree_device_percentages

Get crashfree percentages

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

App Center X-API-Tokens (and basic credentials) are stored encrypted in the Jentic vault (MAXsystem). Agents call operations through scoped tokens — the raw account-wide token never enters agent context, which matters because App Center tokens grant write access across the organization's apps.

Intent-based discovery

Agents search by intent (e.g. 'list crash groups' or 'push a codepush release') and Jentic returns the matching analytics, crash, distribute, or codepush operations with their input schemas, removing the need to navigate App Center's 351-endpoint surface up front.

Time to first call

Direct App Center integration: 3-5 days for auth, owner/app addressing, and pagination over the analytics endpoints. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Firebase API

Firebase covers mobile crash, analytics, and remote config from the Google ecosystem

Pick Firebase when the team is already on Google Cloud; pick App Center for Microsoft-aligned mobile DevOps with CodePush

Alternative

Sentry API

Sentry focuses on crash and error monitoring across mobile, web, and backend

Use Sentry when error monitoring spans mobile and backend; use App Center for end-to-end mobile DevOps including build, distribute, and CodePush

Alternative

Bugsnag API

Bugsnag specialises in stability monitoring and release health across platforms

Choose Bugsnag for cross-platform stability tracking; choose App Center when you also need build, distribute, and CodePush in one tool

Alternative

Rollbar API

Rollbar covers error monitoring and triage across web and mobile

Use Rollbar for error monitoring as a standalone concern; use App Center to combine monitoring with build, release, and CodePush

FAQs

Specific to using App Center Client API through Jentic.

What authentication does the App Center API use?

Two schemes are supported: an X-API-Token header (preferred for service-to-service calls) and HTTP basic auth. Through Jentic the X-API-Token is stored encrypted in the vault (MAXsystem) and never enters agent context — agents receive scoped access only.

Can I push a CodePush release with this API?

Yes. The codepush endpoint family covers deployment creation, release upload, and rollback. Combine it with /v0.1/apps/{owner}/{app}/analytics/crashfree_device_percentages to monitor stability after the release lands.

What are the rate limits for the App Center API?

The OpenAPI spec does not encode explicit rate limits. App Center applies per-token throttling that returns HTTP 429 when exceeded — inspect response headers for live state and back off before retrying.

How do I check crash counts through Jentic?

Run pip install jentic, then search 'list app center crash counts'. Jentic returns the /v0.1/apps/{owner}/{app}/analytics/crash_counts operation with its input schema — load the schema, populate owner and app, and execute. The agent never sees the X-API-Token.

How does the {owner_name}/{app_name} addressing work?

Most app-scoped endpoints take the owner (organization or user) and app name as path parameters. List your apps via GET /v0.1/apps to find the correct values, and prefer using the canonical owner_name shown there to avoid casing mismatches.

Can I run GDPR data exports through this API?

Yes. POST /v0.1/account/test/export and the surrounding GDPR endpoints generate per-account export bundles. Use these for data-subject access request automation rather than manual exports from the App Center portal.