specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: University of Exeter
providerId: university-of-exeter
created: '2026-06-03'
modified: '2026-09-01'
generated: '2026-09-01'
method: derived
reconciled: false
tags:
- Education
- Higher Education
- University
- Rate Limiting
description: >-
  University of Exeter publishes no rate-limit policy for any surface it operates. No 429 was
  triggered and no Retry-After, X-RateLimit-* or equivalent header was observed on any
  Exeter host during probing. The only unauthenticated Exeter-hosted API,
  news.exeter.ac.uk/wp-json/, carries WordPress core's defaults with nothing published on
  top; every other surface is credentialed, so limits (if any) are set per credential and are
  not visible externally.
notes: >-
  Derived from observation, not from a published Exeter policy - there is no rate-limit
  documentation to cite. Corrected 2026-09-01: the prior version named OAI-PMH, IIIF and
  library harvesting endpoints as throttled surfaces; Exeter operates none of those three.
sources:
- https://raw.githubusercontent.com/api-evangelist/university-of-exeter/refs/heads/main/apis.yml
- https://news.exeter.ac.uk/wp-json/wp/v2/posts
responseCodes:
  throttled: 429
  throttled_observed: false
limits:
- name: Undeclared
  scope: client
  metric: requests-per-minute
  limit: not published
  notes: >-
    No published limit on any Exeter-operated surface, and no rate-limit header observed on
    news.exeter.ac.uk/wp-json/, api.exeter.ac.uk or ele.exeter.ac.uk.
policies:
- name: Backoff Strategy
  description: Exponential backoff with jitter; honor Retry-After; harvest during off-peak hours.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com