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.

Install Jentic One Beta

Connect the Blazemeter API Explorer to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blazemeter API Explorer, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 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

GET STARTED

Start building with Blazemeter API Explorer API

Explore with Jentic

View OpenAPI Document

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 Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

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.

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.