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

# Blazemeter API Explorer

The Blazemeter API exposes a slice of Blazemeter, the cloud-based load and performance testing platform. The endpoints in this v4 spec focus on the user-account surface: active sessions, organization multi-test collections, invites, available test-execution locations, private masters and tests, projects, registration, password updates, and user information. Performance and QA teams use these endpoints to wire Blazemeter accounts into onboarding, SSO-related flows, and dashboards that surface a user's tests and projects without scraping the Blazemeter web UI.

## For AI agents

Read user-scoped Blazemeter resources - active sessions, projects, private tests and masters, available locations, and account details. Useful for agents automating Blazemeter user onboarding and dashboards.

## Scope

Does not handle test execution, result reporting, or workspace administration - use for Blazemeter user-scoped account, project, session, and metadata reads only.

## Capabilities

- List a Blazemeter user's active sessions and terminate them on demand
- Enumerate organization multi-test collections accessible to the user
- List the test-execution locations available to the user account
- Pull the private tests and private masters owned by the user
- Manage user account fundamentals: registration, password update, invites, projects
- Surface a user's top items (top) for a quick dashboard overview

## Use cases

### User Account Dashboard for Blazemeter

Build an internal dashboard that surfaces a user's Blazemeter footprint without sending them into the Blazemeter web UI. GET /user/projects, GET /user/tests, GET /user/masters, and GET /user/top together produce a single-page summary of what the user owns and recently ran. The dashboard is a useful starting point for performance-team standups and onboarding-progress checks.

Example prompt: Call GET /user/projects, GET /user/tests, GET /user/masters, and GET /user/top and combine the results into a single dashboard payload.

### Active Session Hygiene

Audit a Blazemeter user's active sessions on a schedule and terminate stale ones. GET /user/active/sessions lists sessions in flight, and POST /user/active/terminate ends a chosen session. This is useful in regulated environments where session lifetimes are bounded by policy and dormant sessions need to be closed promptly.

Example prompt: Call GET /user/active/sessions, identify any session older than the policy ceiling, and POST /user/active/terminate to close it.

### Test Execution Location Pre-Check

Before scheduling a load test the orchestrator confirms which test-execution locations the user can target. GET /user/locations returns the available locations; the orchestrator picks the closest one to the system under test or the one mandated by data-residency rules. This avoids failed runs caused by region restrictions on the user's plan.

Example prompt: Call GET /user/locations, filter for the EU region, and use the chosen location id when scheduling the next load test.

### Onboarding and Invite Tracking

When new performance engineers join a team, an onboarding flow checks GET /user/invites to confirm the Blazemeter invite was issued, then walks the user through GET /user/projects to verify project access. The same flow handles password resets via the /user/password endpoints. This automates the manual click-through that platform owners typically run on day one.

Example prompt: Call GET /user/invites for the new joiner's account, then GET /user/projects to confirm project visibility, and report any missing access.

### Agent-Driven User Footprint via Jentic

An AI agent supporting an SRE asks 'what Blazemeter tests does this user own?' and uses Jentic to call /user/tests on their behalf. Jentic stores the api_key and the agent never sees the raw key. The agent returns a summary of private tests, masters, and projects, which is enough to answer the question without the SRE leaving chat. This makes Blazemeter a usable lookup tool inside higher-level agent workflows.

Example prompt: Use Jentic search for 'list the user's private tests in Blazemeter', load the GET /user/tests schema, then execute and summarise the result.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /user/active/sessions | List active user sessions |
| POST | /user/active/terminate | Terminate an active session |
| GET | /user/locations | List available test-execution locations |
| GET | /user/projects | List user projects |
| GET | /user/tests | List user private tests |
| GET | /user/masters | List user private masters |
| GET | /user/invites | List user invites |

## Key resources

- **User Sessions** — List active sessions and terminate them
- **User Tests and Masters** — Private tests and master test runs owned by the user
- **Projects and Collections** — Projects and organization multi-test collections accessible to the user
- **Locations** — Test-execution locations available to the user
- **Account** — Registration, password updates, invites, and top items

## Why Jentic

- **Setup:** Wiring Blazemeter by hand means passing its api_key as a URL query parameter and keeping that value out of your own request logs. Through Jentic you install once, import Blazemeter from the API Directory, store the api_key once, and your agent calls it.
- **Permission scoping:** The Blazemeter user endpoints carry their target in query parameters, not the URL path, so scope the agent to the operations it needs, such as listing the user's projects, tests, and active sessions. You choose that set, so terminating active sessions is not included unless you add it.
- **Credential handling:** Your Blazemeter api_key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list my Blazemeter private tests' or 'list active Blazemeter sessions', and Jentic returns the matching operation with its query-parameter schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Blackfire API** — Blackfire profiles code-level performance while Blazemeter generates load - together they cover both sides of performance testing.
- **Black Kite API** — Black Kite scores third-party cyber risk while Blazemeter validates performance - both feed go-live readiness.
- **Bland AI API** — Bland AI can voice-page on-call when a Blazemeter test detects regression.

## FAQ

### What authentication does the Blazemeter API use?

The spec declares an api_key passed as a query parameter (security scheme apiKey). Through Jentic the api_key is stored in the encrypted vault and never enters the agent's context - important because Blazemeter's query-parameter auth is otherwise prone to leaking into URL logs.

### Can I list a user's private tests with this API?

Yes. GET /user/tests returns the user's private tests and GET /user/masters returns their private master runs. Together with GET /user/projects this is enough to build a per-user footprint view.

### How do I check available test-execution locations for a user?

Call GET /user/locations. The response lists the regions the user account is entitled to use. Pick the right id before scheduling a run to avoid region-restriction failures.

### What are the rate limits for the Blazemeter API?

The OpenAPI spec does not declare an explicit rate limit. Treat the endpoints as paced for dashboard and onboarding usage rather than high-fan-out polling, and back off on HTTP 429 responses if you sweep across many users.

### How do I list a Blazemeter user's tests through Jentic?

Install with pip install jentic, then use Jentic search with 'list the user's private tests in Blazemeter'. Jentic loads the GET /user/tests schema and executes the call. The api_key is supplied by Jentic from the encrypted vault, not by the agent.

### Does this spec cover load test execution and reporting?

No. The 14 endpoints in this v4 spec are user-scoped account and metadata reads. Triggering test runs and pulling result reports lives on other Blazemeter endpoints not covered here. Use this spec for the user, project, and metadata surface only.

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

Yes. Because you run Jentic One yourself, you decide which Blazemeter operations the agent can call and which credentials it uses, so you can grant read-only calls like GET /user/projects, GET /user/tests, and GET /user/active/sessions while withholding the rest. A destructive operation such as POST /user/active/terminate stays out of the agent's reach unless you explicitly add it. Since the Blazemeter endpoints carry their target in query parameters rather than the path, the allowed operation set is the control point, and your api_key is injected at execution time without ever entering the agent's context.