GitClear · Rate Limits

Gitclear Rate Limits

The GitClear public REST API authenticates with a per-account Bearer API token. GitClear does not publish specific numeric rate-limit values (RPM/RPD) in its public API reference; report endpoints are paginated via a `page` parameter and callers should expect standard throttling responses on excessive usage. Specific per-account limits are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests and page.

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

Tagged areas include Code Analytics, Commit Analytics, Developer Productivity, Diff Delta, and Engineering Metrics.

2 Limits Throttle: 429
Code AnalyticsCommit AnalyticsDeveloper ProductivityDiff DeltaEngineering MetricsRate LimitingQuotasThrottling

Limits

Requests Per Minute (RPM) account
requests
see provider documentation
No public numeric RPM published; not reconciled.
Pagination endpoint
page
paginated
Report, audit, developer, and release endpoints accept a `page` query parameter for result paging.

Policies

Token Authentication
All requests require a valid Bearer API token; invalid tokens return 401.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After header.

Sources