Gradescope · Rate Limits

Gradescope Rate Limits

Gradescope does not publish a generally available public REST API, and it does not document public rate limits or quotas for one. Programmatic integration occurs through LTI 1.3 / LTI Advantage service calls (NRPS, AGS, Deep Linking), whose throughput is governed by the connected LMS and the LTI standard rather than by a published Gradescope API rate-limit policy, and through the autograder framework, where throughput is bounded by container grading capacity rather than by HTTP request limits. No specific limit values are reconciled in this artifact.

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

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

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

Tagged areas include Education, EdTech, Grading, Assessment, and LTI.

3 Limits Throttle: not documented
EducationEdTechGradingAssessmentLTIRate LimitingQuotas

Limits

Public API Rate Limit account
requests
not documented (no generally available public REST API)
Gradescope does not publish a public REST API or its rate limits.
LTI Service Calls (NRPS / AGS / Deep Linking) deployment
requests
governed by LMS and LTI 1.3 standard
Throughput for roster sync and grade passback is mediated by the connected LMS, not a published Gradescope limit.
Autograder Execution assignment
jobs
bounded by grading container resources and timeout
Autograder throughput is constrained by container CPU/memory and configured run timeouts rather than HTTP request limits.

Policies

No Published API Quotas
Gradescope does not document public API quotas because no generally available public REST API is offered.
Backoff Strategy
For LTI integrations, clients should follow the connected LMS guidance and standard exponential backoff with jitter on transient errors.

Sources