Bloomberg · Rate Limits

Bloomberg Rate Limits

Bloomberg's BLPAPI and enterprise data services do not publish numeric rate limits on the open internet; quotas are governed contractually by the Terminal seat license and by data-feed agreements (B-PIPE, Data License). The platform enforces per-application daily caps (notably for BDH/BDP historical and reference data calls) and per-feed bandwidth ceilings, but precise numbers are released only through customer-facing documentation behind the Terminal login.

Bloomberg Rate Limits is the machine-readable rate-limit profile for Bloomberg on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring varies.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include Rate Limiting, Market Data, Financial Services, and Enterprise.

3 Limits Throttle: see BLPAPI session response status Quota: see BLPAPI session response status
Rate LimitingMarket DataFinancial ServicesEnterprise

Limits

BLPAPI request/response (Terminal-connected) account/terminal
varies
see WAPI in Bloomberg Terminal
Daily and monthly caps on number of unique securities and field requests are enforced per Terminal user; exact numbers visible inside the Terminal.
B-PIPE streaming contract
varies
see B-PIPE service-level agreement
Update rate, subscription count, and concurrent session ceilings governed by the negotiated B-PIPE contract.
Bloomberg Data License (EDF / DLWS / HAPI) contract
varies
see Data License agreement
Per-application, per-batch, and redistribution caps are contractual; HAPI request rates published in the Data License Web Services customer documentation.

Policies

Contractual governance
All limits flow from the Terminal Subscription Agreement and the relevant data-feed contract; raise-via-account-manager rather than self-service.
Terminal-bound BLPAPI
BLPAPI sessions normally require a logged-in Terminal on the same workstation; ServerAPI and B-PIPE remove this constraint via licensed gateways.
Backoff
Clients should respect SessionStatus / ServiceStatus events from BLPAPI and back off when slow-consumer or capacity events are signaled.

Sources