canonical: https://jentic.com/apis/testingbot.com/testingbot

# TestingBot API

Access and modify all your TestingBot data through a comprehensive REST API. Build integrations and automate testing workflows. The API exposes 31 endpoints secured with basic authentication.

## For AI agents

Programmatically list available browsers, access your user info. Covers 31 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- List available browsers
- Access your user info
- Edit your user info
- Get team info
- Create a user in your team
- Retrieve a specific user in your team

## Use cases

### Developer Tools Operations

Use the TestingBot API to perform developer tools operations programmatically. The API provides 31 endpoints covering core functionality including list available browsers, access your user info, edit your user info.

Example prompt: Call GET /browsers to list available browsers

### Automated Browsers Management

Automate browsers operations by combining multiple TestingBot API endpoints. Agents can access your user info and then edit your user info in a single workflow.

Example prompt: Call GET /user to access your user info, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TestingBot 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.

Example prompt: Search Jentic for 'list available browsers', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/browsers` | List available browsers |
| GET | `/user` | Access your user info |
| PUT | `/user` | Edit your user info |
| GET | `/team-management` | Get team info |
| POST | `/team-management/users` | Create a user in your team |
| GET | `/team-management/users` | Get users in your team |
| GET | `/team-management/users/{id}` | Retrieve a specific user in your team |
| PUT | `/team-management/users/{id}` | Update a user in your team |

## Key resources

- **Browsers** — Operations for browsers
- **Builds** — Operations for builds
- **Configuration** — Operations for configuration
- **Devices** — Operations for devices
- **Screenshots** — Operations for screenshots

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 50 / 100
- **View full report:** https://jentic.com/apis/testingbot.com/testingbot/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the TestingBot API by hand means learning its HTTP basic auth (API key plus secret) against the api.testingbot.com/v1 host and coding each browser, user, and team-management call yourself. Through Jentic you install once, import the TestingBot API from the API Directory, store the key and secret once, and your agent calls it.
- **Permission scoping:** TestingBot puts the team-member id in the URL path (`/team-management/users/{id}`), so a rule can pin your agent to one team member: it can read that member and nothing else. You choose the operations it may call, so updating a user or team-management settings is not included unless you add it.
- **Credential handling:** Your TestingBot API key and secret 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.
- **Discovery method:** Agents search Jentic by intent such as 'list available browsers' or 'read a team member', and Jentic returns the matching TestingBot API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the TestingBot API use?

The TestingBot 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 list available browsers with the TestingBot API?

Yes. Use the GET /browsers endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TestingBot 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 list available browsers through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list available browsers'. Jentic returns the matching TestingBot API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TestingBot API have?

The TestingBot API exposes 31 endpoints covering browsers, builds, configuration operations.

### Can I limit what my agent is allowed to do with the TestingBot API?

Yes. Because you run Jentic One yourself, your own rules decide which TestingBot operations and credentials your agent may use. TestingBot puts the team-member id in the URL path (`/team-management/users/{id}`), so you can pin the agent to reading one member with GET `/team-management/users/{id}` and nothing else. Write operations such as PUT /user or POST `/team-management/users` are excluded unless you explicitly add them.