specification: API Commons Rate Limits specificationVersion: '0.1' provider: British Columbia Data Catalogue providerId: british-columbia-data-catalogue generated: '2026-09-04' method: probed source: >- Live unauthenticated requests to https://catalogue.data.gov.bc.ca/api/3/action/ with response headers captured, plus a documentation search of https://bcgov.github.io/data-publication/. created: '2026-05-04' modified: '2026-09-04' # REPLACES a 2026-05-04 bulk-sweep scaffold that invented free/professional/enterprise # tiers (10/100/1000 rpm), monthly quotas and X-RateLimit-* headers this API does not # return. See roadmap#35. limit_count: 0 documented: false headers_returned: [] headers: limit: null remaining: null reset: null retryAfter: null policy: null responseCodes: throttled: null limits: [] detail: >- DataBC publishes no rate limits, quotas or throttling policy for the BC Data Catalogue API, and the API returns no rate-limit signalling of any kind. A HEAD against /api/3/action/package_list?limit=1 returned only content-type, content-length, cache-control, server (Werkzeug/1.0.0 Python/3.8.10) and the gateway's x-kong-upstream-latency / x-kong-proxy-latency. No RateLimit-*, X-RateLimit-* or Retry-After header was present, and no 429 was observed. observed: - url: https://catalogue.data.gov.bc.ca/api/3/action/package_list?limit=1 method: HEAD status: 200 headers_seen: - content-type - content-length - cache-control - server - date - x-kong-upstream-latency - x-kong-proxy-latency gateway: vendor: Kong evidence: x-kong-upstream-latency and x-kong-proxy-latency response headers note: >- The surface sits behind DataBC's Kong-based API management service, so throttling may exist at the gateway without being advertised. An agent has no runtime signal to back off on: it would discover a limit only by being cut off. Publishing RateLimit headers (RFC 9331 style) would be the single highest-value runtime addition here. maintainers: - FN: Kin Lane email: info@apievangelist.com