Blazemeter API Explorer

Name: Blazemeter API Explorer API
Brand: Blazemeter API Explorer
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting QaapiKey14 EndpointsREST

For 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.

Quickstart

Get started with Blazemeter API Explorer in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list the user's private tests in Blazemeter"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Blazemeter API Explorer API.

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

GET STARTED

Start building with Blazemeter API Explorer API

Explore with Jentic

View OpenAPI Document

Use for: List a Blazemeter user's active sessions, Get the test-execution locations available to the user, List the user's private tests in Blazemeter, Retrieve the projects a Blazemeter user can access

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

Jentic publishes the only available OpenAPI document for Blazemeter API Explorer, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Blazemeter API Explorer API for, with concrete tasks.

★ 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.

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.

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.

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.

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.

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

14 endpoints — the blazemeter api exposes a slice of blazemeter, the cloud-based load and performance testing platform.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Blazemeter's api_key is passed as a URL query parameter, which makes credential leakage in logs a real concern. Jentic stores the api_key in the encrypted vault and constructs the request server-side, so the agent never holds the raw key and the value never appears in the agent's prompt or tool-call logs.

Intent-based discovery

Agents search Jentic with intents like 'list the user's private tests in Blazemeter' or 'list active Blazemeter sessions' and Jentic returns the matching operation from the 14-endpoint user-scoped spec with its query-parameter schema.

Time to first call

Direct integration: about a day to wire query-parameter auth, credential rotation, and per-user response handling. Through Jentic: under an hour — search, load schema, execute against /user/* endpoints with credentials handled inside Jentic.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Blackfire API

Blackfire profiles code-level performance while Blazemeter generates load — together they cover both sides of performance testing.

Use Blazemeter to drive traffic and Blackfire to profile what happens inside the application during the load run.

Complementary

Black Kite API

Black Kite scores third-party cyber risk while Blazemeter validates performance — both feed go-live readiness.

Pair them in a vendor go-live readiness pipeline that combines security and performance signals.

Complementary

Bland AI API

Bland AI can voice-page on-call when a Blazemeter test detects regression.

Use Bland AI to escalate via voice if a Blazemeter run flags a regression overnight.

FAQs

Specific to using Blazemeter API Explorer API through Jentic.

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.