Bloomberg Data License

The Bloomberg Data License Hypermedia API only accepts requests from IP addresses registered against your Web API application in the Bloomberg Enterprise Console. An app on Replit, Vercel, or AWS Lambda egresses from a rotating address, which Bloomberg rejects, either with a 401 that names your IP as not whitelisted or a connection that closes before any response.

QuotaGuard gives that app a fixed network identity from a single environment variable.

• One-Variable Setup: Set your QuotaGuard connection URL as an environment variable on your app's host, then route your Bloomberg calls through it. Register your two IPs in the Enterprise Console once.
• Two Static IPs That Are Yours: A load-balanced pair assigned to your account. Register both against your Web API application, since traffic can leave from either at any time.
• Covers OAuth and Data Hosts: A Data License integration authenticates at Bloomberg's SSO host and pulls content from the data host. Routing through QuotaGuard sends both out through your two static IPs, with no change to how you authenticate.
• Any Host: Replit, Vercel, AWS Lambda, containers, or your own server. The proxy is read by your HTTP client, so nothing host-specific is required.
• Static Carries It Without Decrypting: Your Bloomberg calls are outbound HTTPS through a CONNECT tunnel, so QuotaGuard sees only host and port, never your payload or credentials. Choose Shield if your compliance review also requires the proxy hop itself to be encrypted.
• EU Data Residency: EU regions in Frankfurt, Ireland, and London, with dedicated EU IPs on Enterprise and a Data Residency add-on from $899 per month.

Scope note: this is for the Data License Hypermedia API (api.bloomberg.com/eap). The Bloomberg Terminal, Desktop API, Server API, and B-PIPE use Bloomberg's own connectivity and are not proxy use cases.

Setting it up? See the step-by-step Bloomberg Data License static IP guide.