generated: '2026-08-27'
method: searched
source: >-
  https://docs.webz.io/docs/webz/news-blogs-forums-errors-limits,
  https://docs.webz.io/docs/webz/cyber-api-errors-limits,
  https://docs.webz.io/docs/webz/reviews-api-errors-limits,
  https://docs.webz.io/docs/webz/data-breach-errors-limits,
  https://docs.webz.io/docs/webz/news-search-api-errors-limits,
  https://docs.webz.io/docs/webz/news-api-lite,
  https://docs.webz.io/docs/webz/fh-api-curated-feed
docs: https://docs.webz.io/docs/webz/news-blogs-forums-errors-limits
summary: >-
  Webz.io meters two independent dimensions on every product: request RATE (about 1 request per
  second per token) and CREDITS (a monthly or prepaid quota consumed per request). Both exhaust into
  the same 429 status, which is the single most important runtime fact for an agent — a 429 here does
  not reliably mean "back off and retry", it may mean "you are out of credits and retrying will never
  succeed". Only the Data Breaches API disambiguates the two, via an X-RateLimit-Reason header.
limit_count: 8
rate_limits:
- scope: per-token, per-endpoint
  api: News / Blogs / Forums
  window: 1 second
  limit: 1
  burst: null
  status_on_exhaustion: 429
  body_on_exhaustion: '{ "detail": "rate limit exceeded" }'
  note: Documented as "by default about 1 request per second per endpoint". Contact support for a higher limit.
- scope: per-token
  api: Reviews
  window: 1 second
  limit: 1
  status_on_exhaustion: 429
  body_on_exhaustion: 'rate limit exceeded'
- scope: per-token
  api: Cyber
  window: 1 second
  limit: 1
  status_on_exhaustion: 429
  body_on_exhaustion: 'rate limit exceeded'
- scope: per-token
  api: Data Breaches
  window: 1 second
  limit: 1
  status_on_exhaustion: 429
  response_headers:
  - 'X-RateLimit-Reason: rate_limit'
- scope: per-token
  api: News Search
  window: null
  limit: null
  status_on_exhaustion: 429
  note: >-
    Documented as "each API token has a maximum number of requests per second" without publishing the
    number. Contact Webz support for a higher limit. This is a documented-but-unquantified limit.
- scope: per-token (recommended, not enforced as published)
  api: Firehose (FH API)
  window: 1 second
  limit: 1
  note: >-
    "The recommended request rate is one call per second. Higher rates require a predefined
    configuration with Customer Support." Page size is 100 posts per response.
- scope: per-account, monthly
  api: News API Lite (free tier)
  window: 1 month
  limit: 1000
  note: Up to 1,000 API calls per month and 10 results per call. Non-commercial use only.
- scope: per-account, monthly quota
  api: Cyber / Reviews
  window: 1 month
  limit: null
  status_on_exhaustion: 429
  body_on_exhaustion: 'Too many requests: used X out of Y allowed in a month'
  note: Quota value is plan-specific and not published.
response_headers:
- name: X-WebHose-Requests-Left
  apis: [Cyber, Reviews]
  meaning: Remaining credit balance for the month.
- name: X-RateLimit-Reason
  apis: [Data Breaches]
  values: [rate_limit, insufficient_credits]
  meaning: >-
    The only header in the whole Webz.io surface that separates a retryable rate-limit 429 from a
    terminal insufficient-credits 429.
body_fields:
- name: requests_left
  apis: [News, Blogs, Forums, News Search]
  meaning: Remaining credit balance, returned in every successful response envelope.
- name: requestsLeft
  apis: [Cyber, Reviews, Data Breaches]
  meaning: Same value, camelCase on the older products.
- name: credits_used
  apis: [News Search]
  meaning: Credits consumed by this search.
credits:
- api: News / Blogs / Forums
  cost: 1 credit per request within the last 31 days; 2-4 credits for older windows
  segmentation_cost: 1 credit
  note: Every page of a paginated result set is a new request and costs credits.
- api: Cyber
  cost: 1 credit per search, segmentation, cached-page and image request
  quota: separate monthly Cyber quota
- api: Reviews
  cost: 1 credit per search and per segmentation request
- api: Data Breaches
  cost: 1 credit per request, including a request that returns 0 records and each Breach Catalog call
- api: News Search
  cost: reported per response in credits_used; failed requests are not charged
- api: Archive
  cost: 1 prepaid credit per post retrieved; charged on actual posts retrieved
  free_allowance: up to 100 posts from the last 30 days, once per account, costing no credits
missing_signals:
- No RateLimit-* (RFC 9331 / draft-ietf-httpapi-ratelimit-headers) headers on any product.
- No Retry-After header documented on any 429.
- No published numeric rate limit for the News Search API.
- Rate-limit 429 and out-of-credit 429 are indistinguishable on News/Blogs/Forums, Reviews and Cyber.