BrowserStack API Documentation

This is the complete API documentation for connecting to the BrowserStack API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet BrowserStack: Run browser automation and inspect plan, browser, build, and session data in BrowserStack Automate. Keep reading to get started.

Quickstart

Before you run your first BrowserStack request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one BrowserStack connection — create or choose one in Connections. Note its connectionId.

Every BrowserStack action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/browserStack/latest/actions/{actionSlug}

You need a MindCloud API Key and a BrowserStack connection. Then call an action such as Get Automate Plan Details:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/browserStack/latest/actions/get-automate-plan-details" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected BrowserStack account that should run the action. MindCloud stores and refreshes the BrowserStack credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

BrowserStack actions

All 19 published actions for this BrowserStack version. Each page documents the endpoint, arguments, and response controls.

• DELETEDelete Build
• DELETEDelete Media File
• DELETEDelete Session
• GETGet Automate Plan Details
• GETGet Browser List
• GETGet Project Details
• GETGet Project Status Badge Key
• GETGet Session Console Logs
• GETGet Session Details
• GETGet Session Logs
• GETGet Session Selenium Logs
• GETList Builds
• GETList Projects
• GETList Sessions In Build
• GETList Uploaded Media Files
• PUTSet Session Status
• PUTUpdate Build Details
• PUTUpdate Project Details
• POSTUpload Media File

Related apps

More IT Operations apps on the Universal API, behind the same REST shape. Or browse all apps.

GitHubNetlifyMySQLPostgreSQLFirebasePagerDutyGoogle Workspace AdminAdalo