Proctorio · Rate Limits

Proctorio Rate Limits

Proctorio does not publish numeric rate limits for its v2 integration API or its result webhooks. The launch API is called once per exam session (to mint a signed candidate, reviewer, or live URL) rather than in high-volume automated loops, so effective throughput is governed by exam volume and the terms of the partner/institution agreement rather than by a documented per-minute request cap. Result webhooks are emitted once per submitted attempt (and can be re-emitted from the Review Center). Signed launch URLs carry an expiry (default 18000 seconds in the official client) which bounds how long a minted URL is valid.

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

It captures 4 rate-limit definitions, measuring requests, seconds, events, and exams.

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

Tagged areas include Online Proctoring, Exam Integrity, Assessment, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Online ProctoringExam IntegrityAssessmentRate LimitingQuotas

Limits

Launch API Requests partner
requests
not published
Called once per exam session; no documented numeric request-rate cap.
Signed URL Expiry session
seconds
18000 (default in official client)
The expire field bounds how long a minted launch URL is valid.
Result Webhook Emission attempt
events
one per submitted attempt (re-emittable)
Proctorio POSTs one result payload per attempt; re-emit from Review Center Export Options.
Exam Volume contract
exams
per agreement
Overall usage is governed by the institution/partner agreement, not a global API limit.

Policies

Signed Request Auth
All launch requests are HMAC-signed with the Proctorio-provisioned consumer key and secret; unsigned or invalid requests are rejected.
URL Expiry
Signed launch URLs expire after the configured window and must be regenerated.
Backoff Strategy
Integrating platforms should implement exponential backoff with jitter and honor Retry-After on any 429 responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/proctorio-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.