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: Cabela's
providerId: cabelas
generated: '2026-09-05'
method: searched
source: >-
  Searched Cabela's own surfaces for published rate limits on 2026-09-05: help.cabelas.com
  and its llms.txt index of ~140 FAQ articles, www.cabelas.com/robots.txt, and DNS for
  api./developer./dev./apis.cabelas.com (no records exist). No API, no developer docs and
  therefore no published limits or runtime rate-limit headers.
created: '2026-05-04'
modified: '2026-09-05'
tags:
  - Retail
  - Outdoor
  - Hunting
  - Fishing
  - Camping
  - E-Commerce
  - Company
  - Rate Limiting
description: >-
  Cabela's publishes no API and therefore no rate limits. This artifact records that
  honest zero. It REPLACES a scaffold written by the 2026-05-04 bulk sweep which invented
  free/professional/enterprise quotas (10/100/1000 requests per minute), an
  X-RateLimit-* header family and backoff, burst and fair-use policies for an API that does
  not exist; none of it was ever harvested from Cabela's.
limit_count: 0
limits: []
headers: {}
responseCodes: {}
policies: []
limits_note: >-
  Zero published rate limits. No rate-limit response headers can be recorded either,
  because there is no API endpoint to observe them on — the only rate-limiting behaviour
  Cabela's exhibits is an Akamai bot-management policy on the www storefront, which returns
  HTTP 403 with a "Site Maintenance" interstitial to non-allowlisted clients. That is edge
  bot defence on a retail website, not an API rate-limit contract, and is deliberately not
  recorded as one.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com