Sauce Labs API

Name: Sauce Labs API
Brand: Sauce Labs API
Availability: InStock

✓ Official Vendor SpecStorageObject Storagebasic79 EndpointsREST

For Agents

Programmatically get jobs for a user, get job details. Covers 79 operations with basic authentication.

Use for: I need to jobs for a user, I want to job details, Search for a job, Find all a job

Not supported: Does not handle payments, communications, or crm - use for storage and databases only.

Sauce Labs provides a comprehensive cloud-based platform for automated testing of web and mobile applications. This API allows you to manage test jobs, builds, accounts, Sauce Connect tunnels, app storage, platform information, test insights, and real devices. The API exposes 79 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Sauce Labs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sauce Labs API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsaucelabs.com%2Fsaucelabs" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsaucelabs.com%2Fsaucelabs" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Sauce Labs API.

Get jobs for a user

Update a job

Delete a job

Stop a running job

List job assets

Use Cases

Patterns agents use Sauce Labs API for, with concrete tasks.

GET STARTED

Start building with Sauce Labs API

Explore with Jentic One

View OpenAPI Document

Automated Jobs Management

Automate jobs operations by combining multiple Sauce Labs API endpoints. Agents can get job details and then update a job in a single workflow.

Call GET /rest/v1/{username}/jobs/{job_id} to get job details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sauce Labs API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'get jobs for a user', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

79 endpoints — sauce labs provides a comprehensive cloud-based platform for automated testing of web and mobile applications.

METHOD

PATH

DESCRIPTION

GET

/rest/v1/{username}/jobs

Get jobs for a user

GET

/rest/v1/{username}/jobs/{job_id}

Get job details

PUT

/rest/v1/{username}/jobs/{job_id}

Update a job

DELETE

/rest/v1/{username}/jobs/{job_id}

Delete a job

PUT

/rest/v1/{username}/jobs/{job_id}/stop

Stop a running job

GET

/rest/v1/{username}/jobs/{job_id}/assets

List job assets

DELETE

/rest/v1/{username}/jobs/{job_id}/assets

Delete job assets

GET

/rest/v1/{username}/jobs/{job_id}/assets/{file_name}

Download a job asset file

GET

/rest/v1/{username}/jobs

Get jobs for a user

GET

/rest/v1/{username}/jobs/{job_id}

Get job details

PUT

/rest/v1/{username}/jobs/{job_id}

Update a job

DELETE

/rest/v1/{username}/jobs/{job_id}

Delete a job

PUT

/rest/v1/{username}/jobs/{job_id}/stop

Stop a running job

GET

/rest/v1/{username}/jobs/{job_id}/assets

List job assets

DELETE

/rest/v1/{username}/jobs/{job_id}/assets

Delete job assets

GET

/rest/v1/{username}/jobs/{job_id}/assets/{file_name}

Download a job asset file

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Sauce Labs API by hand means encoding your username and access key for basic auth, choosing the right us-west-1, us-east-4, or eu-central-1 host, and managing job and asset ids yourself. Through Jentic you install once, import the Sauce Labs API from the API Directory, store the basic credentials once, and your agent calls it.

Permission scoping

Sauce Labs puts the username and job id in the URL path (/rest/v1/{username}/jobs/{job_id}), so a rule can pin your agent to one job. You choose the operations it may call, so a destructive one like deleting a job or its assets is not included unless you add it.

Credential isolation

Your Sauce Labs username and access key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list jobs for a user' or 'download a job asset', and Jentic returns the matching Sauce Labs API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sauce Labs API through Jentic.

What authentication does the Sauce Labs API use?

The Sauce Labs API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I get jobs for a user with the Sauce Labs API?

Yes. Use the GET /rest/v1/{username}/jobs endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Sauce Labs API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get jobs for a user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get jobs for a user'. Jentic returns the matching Sauce Labs API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Sauce Labs API have?

The Sauce Labs API exposes 79 endpoints covering jobs, builds, accounts operations.

Can I limit what my agent is allowed to do with the Sauce Labs API?

Yes. Because you run Jentic One yourself, your own rules decide which Sauce Labs operations and credentials the agent may use. Since the username and job id sit in the URL path, such as /rest/v1/{username}/jobs/{job_id}, you can pin the agent to a single job and allow only read operations like getting jobs for a user or listing job assets. A destructive call such as deleting a job or its assets stays out of reach unless you explicitly add it.

Sauce Labs API

Connect the Sauce Labs API to your agent

Capabilities

Use Cases

Start building with Sauce Labs API

Key Endpoints

Why Jentic?

Related APIs

FAQs