Give Glide a Static Outbound IP With a Relay Function

You built a Glide app that calls an external API, and that API only accepts requests from allowlisted IPs. Glide runs on shared cloud infrastructure, so its outbound calls leave from IPs that change. The fix is to route the call through a fixed exit point. Here's how to do that with a small relay function and QuotaGuard.

Glide Sends Outbound Calls Through the Call API Action and Column

Glide reaches external APIs with the Call API action and the Call API column. You configure an Endpoint, a Method, a Query String, Headers, and a Request Body. That's the full surface. There is no field for an HTTP proxy and no setting for a custom egress IP. Glide's own docs confirm the request leaves directly to the Endpoint you name, and redirects are disabled for security. So you cannot point Glide at a proxy the way a server-side app would set HTTPS_PROXY. The exit IP is Glide's to decide, and it isn't fixed.

A Relay Function Gives Glide's Call API a Static IP

Since Glide can't set a proxy or run a sidecar, you host a tiny relay function instead. It's an AWS Lambda or a Google Cloud Function that egresses through QuotaGuard. Glide's Call API sends its request to the relay's function URL with two headers. The relay reads the target you want and forwards the request through the QuotaGuard connection. Your target API sees the request arriving from QuotaGuard's static IPs, not from Glide.

QuotaGuard assigns two load-balanced static IPs to every subscription, and both stay fixed for the life of the subscription. Allowlist both on the API you're calling. The traffic tunnels end to end on standard HTTPS, so the payload is never decrypted at the proxy. You don't rebuild the relay yourself. QuotaGuard publishes a ready-to-run example and documents the reusable pattern. Deploy the example, set your QuotaGuard connection string, and you're done.

Point the Call API at Your Relay With Two Headers

Deploy the relay from the QuotaGuard lambda-relay example. Set its QUOTAGUARDSTATIC_URL to your connection string and give it a secret relay key. Then in Glide, configure the Call API action to hit the relay's function URL and pass two headers. X-Relay-Key is your shared secret. X-Target-URL is the real API you want to reach. The relay forwards the body and returns the response.

Call API action (Glide)

Endpoint: https://your-relay-id.lambda-url.us-east-1.on.aws/
Method:   POST

Headers:
  X-Relay-Key:  your-relay-secret
  X-Target-URL: https://api.example.com/v1/orders
  Content-Type: application/json

Body:
  { "customer": "123", "status": "paid" }

The same call as curl, so you can confirm the relay works before wiring it into Glide:

curl -X POST "https://your-relay-id.lambda-url.us-east-1.on.aws/" \
  -H "X-Relay-Key: your-relay-secret" \
  -H "X-Target-URL: https://api.example.com/v1/orders" \
  -H "Content-Type: application/json" \
  -d '{"customer":"123","status":"paid"}'

The full pattern, including the relay code and how the headers map to the forwarded request, is documented at quotaguard.com/docs/platforms/static-ip-no-http-proxy.

Confirm the Static IP by Targeting ip.quotaguard.com

Before you allowlist anything, prove the relay egresses through QuotaGuard. Set X-Target-URL to https://ip.quotaguard.com and send the call. The response returns the IP the request left from, which will be one of your subscription's two static IPs. Run it a few times and you'll see both. Those two values are what you hand to the API vendor for their allowlist.

QuotaGuard Static Pricing Starts at $19/Month

Bandwidth is bundled. No per-GB overage fees. A Glide app relaying API calls sits comfortably in the entry tier for most workloads. QuotaGuard Static is the right product here because your relay makes standard HTTPS calls and the payload tunnels end to end, never decrypted at the proxy. Dedicated IPs are available on Enterprise and above. On lower tiers, your subscription's two IPs are still static, but shared with other customers.

QuotaGuard Shield Pricing Starts at $29/Month

Use QuotaGuard Shield only if your Glide app moves regulated data and you need to prove no third party can decrypt it in transit. Shield uses SSL passthrough, so the TLS connection runs end to end between your relay and the destination. The compliance coverage it supports, like HIPAA, PCI-DSS, and SOC 2, is worth the difference when your data requires it. For a standard API allowlist with no regulated payload, Static is the correct choice.

All plans include a 3-day trial. Enterprise plans include a 7-day trial. Credit card required. See the full pricing table at quotaguard.com/products/pricing.

Glide can't set a proxy, but it can call a URL, and that's all the relay pattern needs. Deploy the lambda-relay example, follow the relay setup docs, and point your Call API at it. Your target API sees two fixed IPs from then on. Pick a plan at quotaguard.com/products/pricing and give your Glide app a static outbound IP.