Skip to content
Mango9

Mobile Builder API

Versioned authentication, resources, Studio operations, and native release downloads.

The Mobile Builder API is a versioned sidecar over the same customer-owned projects, permissions, billing rules, and build routes used by Web Studio. Its base path is /api/mobile/v1 on the Builder selected by Central.

Authentication and logout

Start authentication through /api/mobile/v1/auth/{action}. Central selects the customer's pinned Builder and returns a one-time handoff. Exchange that handoff on the selected Builder and send the returned token as Authorization: Bearer <token>.

GET /api/mobile/v1/session returns the token's remaining lifetime. DELETE revokes the current token and clears the secure cookie; deleting a token only in the app is not treated as logout.

Stable v1 operations

The discovery response at GET /api/mobile/v1 includes the exact operations path-and-method manifest. Routes not in that manifest return 404, even when a new Web Studio route is later added under an existing feature family. This keeps v1 stable and prevents control-plane routes from becoming public by inheritance.

All operation requests are re-authorized by their existing Studio handler. Use an X-Idempotency-Key for retryable writes that support it. Streaming build responses retain their existing NDJSON event format.

Read resources and pagination

Read resources live below /api/mobile/v1/resources. Project and analytics lists accept bounded page and limit parameters and return pagination metadata. A project workspace can select a thread by threadId even when that thread is not on the currently displayed thread page.

Analytics contains only persisted first-party or edge traffic. When no samples have been collected, available is false; the API never synthesizes preview metrics. Legacy document attachments include at most a 4,000-character preview with chars and truncated metadata.

Native release artifacts

An accepted managed build first creates a durable submission receipt, then starts the external build. Interrupted local billing is retried from that receipt and its idempotent credit-ledger entry. Customer responses expose only the platform package (.ipa for iOS or .apk for Android), never service logs.

Artifact links returned through the Mobile Builder API remain below /api/mobile/v1/ops/..., support HTTP byte ranges, and require the same bearer session and project/file permissions as the build history.

Errors

Errors use JSON with an error code and an HTTP status. Authentication failures are 401, permission failures are 403, unavailable v1 operations are 404, conflicts are 409, exhausted credits are 402, and temporary dependencies use 502 or 503. Unexpected resource failures also return a requestId that support can match to server logs without exposing infrastructure details.