Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean GitHub API has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 2 scoped observations for GitHub API. The baseline covers Unauthenticated REST requests, Authenticated personal REST requests. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Unauthenticated REST requestsApplies when fetching public data without authentication. | 60 requests per hour | Originating IP address | GitHubAug 22, 2026 |
| Authenticated personal REST requestsSome GitHub Enterprise Cloud app and OAuth contexts have higher limits; search and GraphQL use separate constraints. | 5,000 requests per hour | Authenticated user | GitHubAug 22, 2026 |
Tracked constraints and impact
REST API primary limits, secondary throttling, and reset headers. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current GitHub API baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Primary and secondary rate limits