Harness Rate Limits
Harness publishes its platform rate limits on the developer hub. Limits are enforced at two layers with different keys — an IP-address limit at the edge (Google Cloud Armor) and an API-key limit at the platform. Exhaustion returns 429. Harness reserves the right to change these at any time.
Harness Rate Limits is the machine-readable rate-limit profile for Harness on the APIs.io network, in the API Commons Rate Limits shape.
It captures 7 rate-limit definitions, measuring requests and payloads.
Limit state is signalled in the request, response, absent, and finding response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and serviceUnavailable.
Tagged areas include DevOps, GitOps, Rate Limiting, Quotas, and Throttling.
requestresponseabsentfinding
Limits
Sources
- https://developer.harness.io/harness-platform/use-harness-platform/rate-limits
- https://developer.harness.io/release-notes/platform
- https://www.harness.io/pricing
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.