Skip to main content
Use the Apps API to discover app and build UUIDs, then configure the default Chrome extensions loaded with a web app. All requests require an API key in the X-API-Key header. See API Reference for authentication.

List Apps

GET /api/v1/apps — Returns 200 OK
platform
string
Optional platform filter: ios, android, web, or chrome-extension.
active_build is null when an app has no active build. bundle_id may also be null.

List App Dependencies

List the Chrome extensions attached by default to a web app.
GET /api/v1/apps/{app_id}/dependencies — Returns 200 OK

Attach a Dependency

Attach a Chrome extension app to a web app. Future runs inherit the extension’s active build unless the run request supplies an explicit dependencies override.
POST /api/v1/apps/{app_id}/dependencies — Returns 201 Created
The primary app must have platform web, and the dependency must have platform chrome-extension. Both apps must belong to the API key’s organization.

Detach a Dependency

DELETE /api/v1/apps/{app_id}/dependencies/{dependency_app_id} — Returns 200 OK
Detaching changes future runs only. Historical run results retain the exact extension build UUIDs they used. To override defaults for one run, including running with no extensions, see Run Flows.