Everything you need to test an endpoint.
1,000 requests per run · 10 workers · live metrics · CSV and JSON exports.
API performance workspace
Measure response time, throughput, HTTP errors, and rate limits as they happen. Configure a test, inspect the results, and share a clean report.
Live measurements from your current run.
Explore quota signals and share your findings.
See when HTTP 429 appears and what rate-limit headers the API exposes. One run cannot establish a guaranteed safe rate.
Browser restrictions can hide response headers. A network failure may be caused by CORS, connectivity, or the target server.
Filter results, inspect a request, or export your run.
| # | Method | Status | Latency | Quota Remaining | Response Preview | Inspect |
|---|---|---|---|---|---|---|
| Your request log will appear here after you start a test. | ||||||
1,000 requests per run · 10 workers · live metrics · CSV and JSON exports.
Saved history · scheduled checks · alerts · shared team workspaces.
Pulse at apulse.tech is a free browser-based API load testing tool for checking response time, observed throughput, HTTP status codes, and visible rate-limit behavior. Configure a bounded test, send requests directly to an endpoint you control, and inspect the results in one workspace.
See how long it takes for response headers to arrive and how many requests finish over the run. Your browser, internet connection, and endpoint all affect the measurements.
Review successful responses, HTTP 429, other HTTP errors, network failures, and quota headers exposed to the browser.
Choose a read-only endpoint, set the request count and workers, and start with a small run. Pulse’s free browser runs support up to 1,000 requests.
An API load tester sends controlled requests to an endpoint and records how it responds. Pulse shows response-header latency, observed throughput, HTTP status counts, and rate-limit information an API exposes.
Your browser must be allowed to reach the endpoint. For a cross-origin API, its CORS policy needs to allow browser requests from the Pulse website. Use only endpoints you own or have permission to test.
No. A browser run shows observations from one device and one period. It does not establish a guaranteed safe rate or production capacity.
None detected