https://console.phoneuse.com/apps). Choose your phone, then select Install
on an available app. The App Store selects an approved build and saves the
request. You can close the page while the server continues checking the
installation.
The result becomes Installed after a fresh phone inventory confirms that
build. An unconfirmed result holds further installation on that phone while the
server checks the original request. Reopening Apps shows the same saved result.
The CLI and the MCP tools do not install apps. They can read and refresh the
apps currently installed on a phone, and each points you to the Apps page.
Inventory can include apps installed through other routes; it does not require
an App Store request to exist.
Customer APK uploads, custom app libraries, and arbitrary URL installation are
retired, including public custom APK job history. Original request recovery and
accepted App Store results remain available.
Availability depends on the phone’s current installation capability and the
approved build being enabled. A phone reports installApp: "managed_store" in
its capabilities when apps can only be installed from the App Store.
The REST API
The Console uses the managed App Store REST operations, and they are available to other callers with the same permissions. They are described under Apps in the API reference. Installing is a write that must carry anIdempotency-Key
header in one exact form, because the server uses it to recognise the same
request again:
who = JSON.stringify([orgId, subject]), wheresubjectis the signed-in person’suserId, or theapiKeyIdwhen an API key makes the call. TheapiKeyIdis theidfield ofGET /v1/api-keys/current(not itskeyId, which is the public half of the token).payload = JSON.stringify([who, deviceId, scopeId, appId, buildId]).scopeIdisuser_0.- Take the SHA-256 of
payloadas lowercase hex and keep the first 24 characters. - Join them as
store.v2.<those 24 characters>.<a new lowercase UUID>.
orgId org_example, apiKeyId key_example, deviceId
device_example, scopeId user_0, appId telegram, buildId v12.10.1
and UUID 6f1c2a52-3b6e-4d0c-9a57-0d3c8f0b1e11 give:
400. If an
answer is lost, send the same body with the same key to get the same
installation back, or read it with GET /v1/app-store/installations/by-request/{requestKey}.
A second key is a new request and is refused while the phone is held.