JetBrains · Rate Limits

Jetbrains Rate Limits

JetBrains REST APIs (TeamCity, YouTrack, Space, Hub) are most commonly self-hosted, so raw request rate is bounded by the customer's server capacity rather than a vendor-side per-second cap. The two SaaS surfaces — JetBrains Space cloud and YouTrack InCloud — apply per-token throttling to protect shared infrastructure; published numbers are general guidance, with production raises arranged via support. JetBrains AI uses an AI-credit model where rate is bounded by remaining credits per subscription.

4 Limits Throttle: 429
Rate LimitingDeveloper ToolsIDEDevOps

Limits

YouTrack InCloud REST API token
requests_per_second · second
30
Soft cap per permanent token / OAuth client on InCloud. Self-hosted YouTrack is bounded by your server hardware.
Space HTTP API token
requests_per_minute
see organization plan
Per-organization throttling; raise via JetBrains support for production integrations.
TeamCity REST API server
varies
bounded by self-hosted capacity
TeamCity REST API has no provider-side rate limit; throughput is governed by the customer's TeamCity server and database. TeamCity Cloud applies per-tenant fair-use throttling.
JetBrains AI subscription
ai_credits
per AI Pro / AI Ultimate subscription
Throughput is bounded by remaining AI credits for the active subscription tier.

Policies

Backoff
Honor Retry-After on 429 / 503 and back off exponentially with jitter.
Pagination
Use the documented `top` and `skip` (or cursor) parameters to avoid retrieving large collections in one call.
Self-hosted vs SaaS
Self-hosted (TeamCity On-Prem, YouTrack Server, Hub) limits are governed by your hardware. Cloud (Space, YouTrack InCloud) limits are governed by JetBrains gateway throttling.
AI credits
JetBrains AI consumes credits per request and per token; users hitting their cap can upgrade tier or wait for the monthly reset.

Sources