Testmo · Rate Limits

Testmo Rate Limits

Testmo does not publish fixed numeric per-minute rate limits for its REST API in the public documentation reviewed. The API is per-instance (https://{instance}.testmo.net/api/v1) and read-oriented, so throughput is primarily governed by pagination rather than a documented request cap. All list endpoints are paginated with page and per_page parameters (per_page defaults to 100), and responses include prev_page, next_page, and last_page so clients page through large result sets rather than pulling everything at once. Bulk write operations in the beta test case management API are capped by payload size - up to 100 cases or folders per request, and up to 20 attachments per upload.

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

It captures 5 rate-limit definitions, measuring requests, entries, cases, folders, and attachments.

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

Tagged areas include Test Runs, Test Management, Rate Limiting, and Quotas.

5 Limits Throttle: 429
Test RunsTest ManagementRate LimitingQuotas

Limits

REST API Requests instance
requests
not published
No fixed numeric request-rate limit is documented for the Testmo REST API.
List Pagination endpoint
entries
per_page (default 100)
All list endpoints paginate with page and per_page; responses include prev_page, next_page, last_page.
Bulk Case Operations request
cases
100 per request
Beta test case management API creates, updates, and deletes cases in bulk up to 100 per request.
Bulk Folder Operations request
folders
100 per request
Beta test case management API creates, updates, and deletes folders in bulk up to 100 per request.
Attachment Upload request
attachments
20 per request
Beta test case management API uploads up to 20 attachments per bulk request.

Policies

Pagination
Use page and per_page to page through results; follow next_page until it is null.
Field Expansion
Use the expands parameter to fetch related resources (for example users, issues, automation_links) in one request instead of many.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on any HTTP 429 responses.

Sources