Trunk · Rate Limits

Trunk Rate Limits

The Trunk REST API (api.trunk.io) is an authenticated HTTP API using the x-api-token header and standard HTTP response codes. Trunk does not publish explicit numeric request-per-minute rate limits in its public API reference; list endpoints are paginated (page_size 1-100) which bounds response volume, and Flaky Tests uploads are processed periodically rather than in real time. Usage on the platform is metered by test spans per committer rather than by API call rate. Specific throttling thresholds are not reconciled in this artifact.

Trunk Rate Limits is the machine-readable rate-limit profile for Trunk on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests, rows, and uploads.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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

Tagged areas include Developer Tools, CI/CD, Flaky Tests, Merge Queue, and Rate Limiting.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Developer ToolsCI/CDFlaky TestsMerge QueueRate LimitingQuotasThrottling

Limits

REST API Requests account
requests
see provider documentation
No public numeric RPM/RPD published; authenticated via x-api-token.
List Endpoint Page Size request
rows
100
page_query.page_size is bounded to 1-100 on list endpoints.
Test Result Uploads account
uploads
see provider documentation
Uploaded test results are processed periodically (not real-time); allow ~1 hour before results appear.

Policies

Pagination
List endpoints return paginated results with next/prev/last page tokens; page through rather than requesting large windows.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

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/trunk-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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