Bugcrowd API

QuotaGuard routes customer-controlled Bugcrowd API requests through the two fixed public IPv4 addresses assigned to its subscription. Add both addresses to the specific API token through Edit IP Allowlist so either healthy QuotaGuard route can satisfy the source restriction. QuotaGuard has provided static-IP proxy service since 2013.

• Per-Token IP Allowlist: Bugcrowd lets an API token accept calls only from approved IPv4 addresses or ranges. Multiple entries are supported, so both QuotaGuard addresses can remain registered.
• Two-Minute Setup: Configure the customer-controlled HTTP client to use its QuotaGuard proxy connection, confirm the observed source, and add both dashboard addresses to the Bugcrowd token.
• Token Controls Preserved: Bugcrowd still authenticates the token, applies the owner's role and permissions, and uses the token's pinned API version. QuotaGuard supplies network identity without replacing those controls.
• Multi-Platform Support: Use the same pair from Heroku, Render, Railway, Fly.io, AWS Lambda, Vercel, Netlify Functions, Kubernetes, or a direct VPS when the workload controls an HTTP or HTTPS client.
• Production-Grade Reliability: Each subscription receives two load-balanced static IPv4 addresses with health checks and automated failover. Keep both on the token Allowlist so either healthy source remains accepted.
• Shield for Regulated Data: The HTTPS session to Bugcrowd stays encrypted on both products. Shield additionally encrypts the customer-to-proxy hop when required by the customer's data or network policy.

Bugcrowd allowlist note: The API token Allowlist is optional and belongs to one credential. It is separate from Bugcrowd's organization-level IP Restrictions for admin-user access, and it does not replace token authentication or role-based authorization.