FAQs
Common questions about Bugcrowd API static IPs and QuotaGuard.
Does the Bugcrowd API require a static IP?
Only when an API token has an Allowlist configured. Bugcrowd describes the token allowlist as an optional additional security control and rejects API calls made with that token from an unlisted source. If the token has no source restriction, a static IP is not required for this specific gate.
Where do I configure the Bugcrowd API token Allowlist?
Open your profile's API Credentials page, find the token under Current credentials, and select Edit IP Allowlist. Bugcrowd accepts an IPv4 address or range and lets you add multiple entries. Its current API documentation says only IPv4 is supported.
Which QuotaGuard addresses should I add to Bugcrowd?
Add both individual IPv4 addresses shown for the relevant QuotaGuard subscription. Do not add the proxy hostname or assume that only one address will answer, because QuotaGuard load balances and fails over across the pair. Both entries must remain approved for the token to work through either healthy route.
Is the API token Allowlist the same as Bugcrowd organization IP Restrictions?
No. The API token Allowlist is attached to one credential and controls calls made with that token. Bugcrowd's organization-level IP Restrictions setting applies to admin users accessing organization data and has different partial-access behavior for unlisted users. Configure the control that matches the traffic you actually need to restrict.
Does QuotaGuard replace Bugcrowd token authentication?
No. Bugcrowd still authenticates the API token and authorizes resources according to the token owner's role. QuotaGuard supplies the stable network source only, so the token, its permissions, and its pinned API version remain part of every accepted request.
How long does the QuotaGuard side of setup take?
The network work is limited to routing the customer-controlled HTTPS client through QuotaGuard and adding both dashboard addresses to the token's Allowlist. The actual time depends on whether the client already supports an authenticated HTTP proxy and whether the operator can edit that Bugcrowd credential. Confirm the observed egress address before relying on the rule.
Should I use QuotaGuard Static or Shield for the Bugcrowd API?
Use Static for ordinary non-regulated HTTPS automation when a standard authenticated proxy meets the customer's policy. Use Shield when the customer-to-proxy hop must also be TLS-encrypted or the workflow carries regulated data. With either product, the HTTPS session to Bugcrowd remains encrypted and QuotaGuard does not decrypt its payload.
Can I get dedicated IPs for the Bugcrowd API?
Yes. Dedicated IPs and proxy resources are included on direct Enterprise plans, currently $219 per month for QuotaGuard Static and $269 per month for QuotaGuard Shield. Starter, Production, and Business use shared static IP pairs, but each subscription still receives its own two-address pair to place on the token Allowlist.
How should I update the Bugcrowd token Allowlist later?
Add the replacement source before removing the old one, verify a harmless API request through the new path, and retain both active QuotaGuard addresses. Bugcrowd supports multiple entries, which allows an overlap during a controlled network or token migration. Do not delete the old credential until the replacement path and intended API version are working.
Does this integration make Bugcrowd outgoing webhooks use QuotaGuard IPs?
No. This page covers outbound API requests traveling from the customer's application through QuotaGuard to Bugcrowd. Bugcrowd outgoing webhooks travel from Bugcrowd to the customer's receiver in the opposite direction and need their own endpoint authentication and access-control design.