specification: API Commons Rate Limits
specificationVersion: '0.1'
provider: Barclays
providerId: barclays
generated: '2026-09-04'
modified: '2026-09-04'
method: searched
source: openapi/ (26 first-party OpenAPI 3.1 documents) + https://developer.barclays.com portal search
limit_count: 0
limits: []
documented: false
note: 'Barclays declares that throttling exists but never says what the limits are. 99 operations across the estate
  declare an HTTP 429 "Too Many Requests" response — the Confirmation of Funds, Payment Initiation and Account and
  Transactions contracts describe it as "Server received a large number of requests from a single party in a given
  amount of time" — but no operation declares a RateLimit-*, X-RateLimit-* or Retry-After response header, and no
  numeric limit, window, burst or quota is published anywhere on the anonymous surface. An agent can detect exhaustion
  from the status code and nothing else: it cannot budget ahead of time, and it is not told how long to wait. REPLACES
  a 2026-05-04 bulk-sweep scaffold that carried invented 10/100/1000 rpm tiers and an invented X-RateLimit-* header
  set that these contracts do not declare.'
signals:
  status_code: 429
  operations_declaring_429: 99
  response_headers: []
  retry_after: false
  policy_header: false
evidence:
- url: https://developer.barclays.com/api/apis/versions/1918e4d6-a63c-4123-a2e6-12b0c7540002.bdn/design?specification=oas31
  status: 200
  result: 429 declared, no rate-limit response headers
- url: https://developer.barclays.com/api/search?q=rate%20limit
  status: 200
  result: 41 hits, none a rate-limit policy document
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com