University of Oxford · Rate Limits

University Of Oxford Rate Limits

The University of Oxford publishes no rate-limit table, no quota and no Retry-After header on any institution-operated surface, and none was observed in probing. What it does publish, uniquely for ORA, is an etiquette policy in prose: harvesters wanting all or a large sample of the repository are asked to contact the service first, and Oxford states that unexpected spidering or scraping may lead to access being blocked. That is a social control enforced by a human decision, not a technical limit a client can read. Separately, ora.ox.ac.uk sits behind Cloudflare and issues managed challenges (HTTP 403, cf-mitigated: challenge) to non-browser clients on some paths — bot mitigation rather than rate limiting, but the practical failure mode a naive client will hit first.

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

It captures 4 rate-limit definitions, measuring unspecified.

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

Tagged areas include Education, Higher Education, University, and Rate Limiting.

4 Limits Throttle: 429
EducationHigher EducationUniversityRate Limiting

Limits

ORA OAI-PMH client
unspecified
none published
Oxford asks bulk harvesters to make contact first (https://ora.ox.ac.uk/api). Scheduled maintenance Tuesdays 07:00-09:00 UK time may return 503.
ORA search / object JSON client
unspecified
none published
Undocumented endpoint; no limit stated. robots.txt disallows /?q*, /?f*, /?page* and /export_csv_search_results, which is the closest thing to a stated automation boundary.
Digital Bodleian IIIF client
unspecified
none published
Image API info.json advertises maxWidth 4000 and maxHeight 4000 — a per-request size ceiling, not a rate limit.
Oxford Text Archive OAI-PMH client
unspecified
none published

Policies

Contact before bulk harvest
Oxford explicitly asks would-be bulk downloaders of ORA to get in touch so the service can advise on approach.
Backoff Strategy
No Retry-After is emitted anywhere; clients should apply exponential backoff with jitter on their own initiative and respect the published Tuesday maintenance window.

Sources