generated: '2026-09-17'
method: searched
source: https://developers.forem.com/api/v0 (per-endpoint "Rate limiting" notes) + live response headers on https://dev.to/api/articles
docs: https://developers.forem.com/api/v0
limit_count: 2
headers:
  limit: null
  remaining: null
  reset: null
  retry_after: null
  note: No RateLimit-*, X-RateLimit-* or Retry-After header was observed on a live 200 from https://dev.to/api/articles
    (2026-09-17). The response does carry x-request-id and x-runtime, so an agent can correlate a call but cannot
    read its remaining budget. Limits are discoverable only by reading the docs or by hitting 429.
response_codes:
  throttled: 429
  throttled_label: Too Many Requests
limits:
- operation: createArticle
  method: POST
  path: /api/articles
  scope: per-api-key
  limit: 10
  window: 30s
  burst: null
  evidence: 'https://developers.forem.com/api/v0 — "Rate limiting: There is a limit of 10 requests per 30 seconds."'
- operation: updateArticle
  method: PUT
  path: /api/articles/{id}
  scope: per-api-key
  limit: 30
  window: 30s
  burst: null
  evidence: 'https://developers.forem.com/api/v0 — "Rate limiting: There is a limit of 30 requests per 30 seconds."'
note: Only the two article write operations carry a published limit. The remaining ~137 operations of the Forem
  API V1 surface document no limit at all, and the V1 OpenAPI declares no 429 response on any operation — the V0
  reference is the only place a number appears. Forem is open source, so a self-hosted instance can override these
  via configuration; the numbers above are DEV's published values.