Give Bardeen a Static Outbound IP With a QuotaGuard Relay

Bardeen runs your automations, but its HTTP action only lets you set a URL, headers, and a body. There's no proxy field and no place to pin an outbound IP. So when a target API sits behind a firewall that allowlists source IPs, Bardeen's requests get rejected. The fix is a small relay function you host once, then call from Bardeen like any other endpoint.

A Relay Function Gives Bardeen Two Static Outbound IPs

Bardeen can't set an HTTP proxy and can't run a sidecar process. That rules out the usual ways to pin an egress IP. The pattern that works is a relay. You deploy a small function on AWS Lambda or a Google Cloud Function. That function egresses through QuotaGuard, so the API on the other end always sees a fixed pair of addresses. QuotaGuard assigns two load-balanced static IPs to every subscription, and the relay forwards Bardeen's request through both, so the target API sees a stable pair instead of a rotating cloud IP. Allowlist both IPs in the target firewall and Bardeen's calls go through.

QuotaGuard Static is the right product for standard HTTPS API calls. The payload is tunneled end to end and is never decrypted at the proxy. There's a ready-to-run relay you can copy instead of building one from scratch. See the Lambda relay example and the static IP without an HTTP proxy guide.

Bardeen's HTTP Action Calls the Relay With Two Headers

Once the relay is deployed, you point Bardeen's HTTP action at the relay function URL. You pass two headers. X-Relay-Key is a shared secret that stops strangers from using your relay. X-Target-URL is the real API you want to reach. The relay reads those headers, forwards the request through the QUOTAGUARDSTATIC_URL connection, and returns the response to Bardeen.

Configure Bardeen's HTTP action (its HTTPS GET/POST command) like this:

Action:  HTTP request (POST)
URL:     https://your-relay-id.lambda-url.us-east-1.on.aws/
Headers:
  X-Relay-Key:  your-secret-relay-key
  X-Target-URL: https://api.example.com/v1/records
Body:
  { "field": "value" }

The same call as a curl command, so you can test the relay outside Bardeen first:

curl -X POST "https://your-relay-id.lambda-url.us-east-1.on.aws/" \
  -H "X-Relay-Key: your-secret-relay-key" \
  -H "X-Target-URL: https://api.example.com/v1/records" \
  -d '{"field":"value"}'

The relay URL above is your own function's URL, not a QuotaGuard host. The static IPs come from the QUOTAGUARDSTATIC_URL connection inside the relay. Your region is set when you sign up, so pick the one closest to your target API. Changing it later means contacting QuotaGuard support.

Confirm the Static IPs With a Quick Relay Test

Before you allowlist anything, prove the egress works. Point X-Target-URL at the QuotaGuard IP check endpoint. It returns one of your two static IPs.

curl -X POST "https://your-relay-id.lambda-url.us-east-1.on.aws/" \
  -H "X-Relay-Key: your-secret-relay-key" \
  -H "X-Target-URL: https://ip.quotaguard.com"

Run it a few times. You'll see both IPs across the responses because the pair is load balanced. Copy both into the target firewall's allowlist. Then swap X-Target-URL back to your real API and run the Bardeen automation.

QuotaGuard Static Pricing Starts at $19/Month

Bandwidth is bundled and there are no per-GB overage fees. Bardeen automations that call a handful of APIs stay well inside the entry tier. Dedicated IPs are available on Enterprise and above. On lower tiers, your subscription's two assigned IPs are still static, but shared with other customers.

QuotaGuard Shield Pricing Starts at $29/Month

Shield costs slightly more than Static at each tier because SSL passthrough adds routing overhead. Use Shield instead of Static only when you handle regulated data and need to meet standards like HIPAA, PCI-DSS, or SOC 2. Shield uses SSL passthrough, so QuotaGuard doesn't decrypt your data. For standard Bardeen API calls, Static is the correct choice.

All plans include a 3-day trial. Enterprise plans include a 7-day trial. Credit card required.

Bardeen doesn't ship a proxy setting, but the relay closes that gap cleanly. Deploy the function once, call it from your HTTP action, and every request leaves from the same two static IPs. Start with the ready-to-run relay repo, follow the relay setup docs, and see the full plan lineup at quotaguard.com/products/pricing.