Bbandt Corp Rate Limits
Truist publishes NO numeric rate limits. What the contracts do publish is the SHAPE of the throttling: 25 of the 31 operations declare a 429 response, and the examples name two distinct Apigee-style mechanisms — a spike arrest (code 1207, "Traffic spike, too many requests") and a quota (code 1207/1208, "Quota violation, too many requests"). Neither the per-second rate nor the quota size nor the window is stated anywhere on the anonymous surface; capacity is set per application during onboarding. No RateLimit-*, X-RateLimit-* or Retry-After header is declared on any 429 response, so a client cannot read its remaining budget at runtime — it only learns, after the fact, which of the two limiters it hit.
Bbandt Corp Rate Limits is the machine-readable rate-limit profile for BB&T Corp (Truist) on the APIs.io network, conforming to the API Commons Rate Limits specification.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Banking, Open Banking, Truist, and Rate Limiting.
Policies
Sources
- https://developer.truist.com/assets/data/swagger-prod/retail-accounts.yaml
- https://developer.truist.com/assets/data/swagger-prod/commercial-credit-transfers-oas-v2.yaml
- https://developer.truist.com/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.