Microsoft Azure 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.

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.

Jentic One on Github

Install Jentic One Beta

Connect the App Center Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the App Center Client, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fappcenter.ms%2Fappcenter" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fappcenter.ms%2Fappcenter" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

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

Push CodePush releases to live mobile apps without app-store re-review

GET STARTED

Start building with App Center Client API

Explore with Jentic One

View OpenAPI Document

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

GET

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

List audience definitions

GET

/v0.1/api_tokens

List API tokens for the account

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring App Center by hand means managing its X-API-Token header alongside basic auth and navigating a large build, distribute, crash, and analytics surface yourself. Through Jentic you install once, import the App Center API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

App Center puts owner_name and app_name in the URL path (/v0.1/apps/{owner_name}/{app_name}/...), so a rule can pin your agent to one app's analytics and crash groups. You choose the operations it may call, so account-wide reads like listing API tokens are not included unless you add them.

Credential isolation

Your App Center API token and basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list crash groups' or 'get active device counts', and Jentic returns the matching App Center operation with its input schema so the agent calls the right endpoint without navigating the full endpoint surface up front.

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 (your Jentic One instance) 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.

Can I limit what my agent is allowed to do with the App Center API?

Yes. Because you run Jentic One yourself, your own rules decide which App Center operations and credentials the agent may use. Since App Center puts owner_name and app_name in the URL path (/v0.1/apps/{owner_name}/{app_name}/...), you can pin the agent to a single app's analytics and crash group reads, such as GET /v0.1/apps/{owner_name}/{app_name}/analytics/crash_groups. You choose the operations it may call, so account-wide actions like listing API tokens stay excluded unless you add them.