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: medium
providerId: medium
created: '2026-05-04'
modified: '2026-09-17'
generated: '2026-09-17'
method: searched
source: https://github.com/Medium/medium-api-docs
tags:
  - Rate Limiting
  - Quotas
  - Throttling
description: >-
  Medium publishes NO rate limits for its REST API. Its documentation (Overview, Authentication,
  Resources, Testing) contains no limit, quota, throttle or 429 reference, declares no
  RateLimit-*/X-RateLimit-*/Retry-After response header, and none of the six refined OpenAPIs in
  this repository declares a 429 response. A client therefore has no runtime signal at all: it
  cannot read a remaining budget, cannot learn a reset time, and has no documented backoff contract.
limit_count: 0
limits: []
headers: {}
responseCodes: {}
policies: []
note: >-
  REPLACES A FABRICATED SCAFFOLD. The previous version of this file published five limits across
  free/professional/enterprise tiers (10, 100 and 1,000 requests per minute; 1,000 and 100,000
  requests per month; burst ceilings of 20/200/5,000) and a full X-RateLimit-* header set. Medium
  documents none of it — those were bulk-sweep scaffold defaults (method: generated, dated
  2026-05-04) presented as provider behaviour. A limit_count of 0 with this note is the honest
  measurement, and it matters: an agent told to expect Retry-After on a 429 would be relying on a
  header Medium never sends.
evidence:
  - url: https://github.com/Medium/medium-api-docs
    status: 200
    finding: >-
      grep for rate limit / 429 / quota / throttle across the full README returns no match outside
      the table of contents.
  - url: https://api.medium.com/v1/me
    status: 401
    finding: >-
      Live unauthenticated response carries no RateLimit-*, X-RateLimit-* or Retry-After header.
maintainers: []