TestRail · Rate Limits

Testrail Rate Limits

TestRail Cloud rate-limits the API to protect shared performance. Published limits are approximately 180 requests per minute on TestRail Professional Cloud and 300 requests per minute on TestRail Enterprise Cloud. When a client exceeds the limit, the API returns HTTP 429 Too Many Requests with a Retry-After header indicating how many seconds to wait before retrying. Self-hosted TestRail Server / Enterprise installations do not impose built-in API rate limits - throughput is bounded by the customer's own infrastructure. To stay under Cloud limits, TestRail recommends using bulk endpoints (for example add_results_for_cases instead of many add_result calls), adding a delay between calls, and upgrading to Enterprise Cloud for a higher ceiling.

Testrail Rate Limits is the machine-readable rate-limit profile for TestRail on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and records.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Test Management, QA, Testing, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Test ManagementQATestingRate LimitingQuotasThrottling

Limits

Professional Cloud API Requests instance
requests
~180 per minute
TestRail Professional Cloud published request-rate limit.
Enterprise Cloud API Requests instance
requests
~300 per minute
TestRail Enterprise Cloud published request-rate limit (higher ceiling).
Self-Hosted (Server / Enterprise) deployment
requests
none built-in
No API rate limit is enforced by TestRail Server; bounded by your own infrastructure.
Bulk GET Page Size endpoint
records
250 per response
Bulk get_ endpoints return up to 250 records; use limit (1-250) and offset to page.

Policies

Retry-After
429 responses include a Retry-After header with the number of seconds to wait before the next request is allowed.
Prefer Bulk Endpoints
Use bulk endpoints (add_results_for_cases, add_results) instead of many single-record calls to reduce request volume.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Upgrade Tier
TestRail Enterprise Cloud raises the per-minute request ceiling relative to Professional Cloud.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/testrail-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.