LambdaTest API Documentation

This is the complete API documentation for connecting to the LambdaTest 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 LambdaTest: Manage LambdaTest web automation builds, sessions, tunnels, files, logs, concurrency, supported platforms, resolutions, geolocation IPs, and auto-heal test insights through the official LambdaTest Automation API. Keep reading to get started.

Quickstart

Before you run your first LambdaTest 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 LambdaTest connection — create or choose one in Connections. Note its connectionId.

Every LambdaTest action uses the same URL pattern:

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

You need a MindCloud API Key and a LambdaTest connection. Then call an action such as Download Pre-Run File:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/lambdaTest/latest/actions/download-pre-run-file" \
  --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 LambdaTest account that should run the action. MindCloud stores and refreshes the LambdaTest 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.

LambdaTest actions

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

• DELETEDelete Build
• DELETEDelete File Extension
• DELETEDelete Pre-Run File
• DELETEDelete Session
• DELETEDelete Tunnel
• DELETEDelete User File
• GETDownload Pre-Run File
• GETDownload Session Full HAR
• GETDownload Session Full HAR V2
• GETDownload Session Network HAR
• GETDownload Session Network HAR V2
• GETDownload User File
• GETGet Auto-Heal Test
• GETGet Build
• GETGet Geolocation IPs
• GETGet Organization Concurrency
• GETGet Session
• GETGet Session Command Logs
• GETGet Session Command Logs V2
• GETGet Session Console Logs
• GETGet Session Console Logs V2
• GETGet Session Exceptions
• GETGet Session Network Logs
• GETGet Session Network Logs V2
• GETGet Session Screenshots
• GETGet Session Selenium Logs
• GETGet Session Selenium Logs V2
• GETGet Session Terminal Logs
• GETGet Session Video
• GETGet Test Exceptions
• GETGet Test Video
• GETList Builds
• GETList File Extensions
• GETList Platforms
• GETList Pre-Run Files
• GETList Resolutions
• GETList Sessions
• GETList Tunnels
• GETList User Files
• PUTStop Build
• PUTStop Session
• PUTUpdate Build
• PUTUpdate Session
• POSTUpload File Extension
• POSTUpload Pre-Run File
• POSTUpload User File
• GETValidate Pre-Run File

Related apps

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

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms