Give Tray.io a Static Outbound IP With a Lambda Relay

Tray.io runs your workflows on its managed cloud. The HTTP Client connector makes outbound API calls from Tray's shared infrastructure, and it has no field for a customer-set proxy. When a partner API only accepts traffic from an allowlisted IP, you need a fixed origin that you control. A small relay function solves this.

Tray.io Needs a Relay Because the HTTP Client Connector Has No Proxy Setting

The Tray.io HTTP Client connector covers headers, TLS, and auth. It does not expose a proxy URL field, so you can't point outbound calls at an HTTP proxy from inside a workflow. That means you can't force Tray's calls to leave from an IP you own using connector config alone.

Tray does publish shared public IPs, and you can allowlist them. Two things make that a weaker fit for a strict partner API. The public IPs are shared across Tray customers, so a partner allowlisting them is trusting every Tray tenant, not just you. And per Tray's own docs, some outbound traffic like OAuth does not necessarily originate from those IPs. Verify current behavior against Tray's public IP documentation before you rely on it.

A relay gives you a fixed origin you control. You host a small function that egresses through QuotaGuard. QuotaGuard assigns two load-balanced static IPs per subscription, and the relay forwards every Tray.io call through that pair, so the target API sees the same two IPs every time. You allowlist both.

A Lambda Relay Gives Tray.io Calls Two Static IPs

You host a small relay function on AWS Lambda or a Google Cloud Function. The relay reads two headers, egresses through QuotaGuard's connection, and returns the response. Tray.io calls the relay instead of the target API directly. The full pattern, including a ready-to-run example, is documented at the QuotaGuard no-proxy relay guide and the lambda-relay repo. Deploy that once.

The relay reads the target from an X-Target-URL header, checks a shared secret in X-Relay-Key, then forwards the request through the QUOTAGUARDSTATIC_URL connection your subscription provides. The target API sees your two static IPs.

In your Tray.io workflow, set the HTTP Client connector to call the relay's function URL and pass the two headers. The X-Target-URL header holds the real API you want to reach.

# Tray.io HTTP Client connector step
Method: GET
URL: https://your-relay-id.lambda-url.us-east-1.on.aws/
Headers:
  X-Relay-Key: your-relay-secret
  X-Target-URL: https://api.example.com/v1/orders

The same call as curl, which is useful for a quick test before you wire it into a workflow:

curl -X GET "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"

To confirm the static IPs are in play, point X-Target-URL at https://ip.quotaguard.com. It returns one of your two static IPs. Run it twice and you'll see the pair.

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

Allowlist both IPs with the partner API. Tray.io keeps calling the relay, the relay egresses through QuotaGuard, and your outbound origin stays fixed.

QuotaGuard Static Pricing Starts at $19/Month

QuotaGuard Static is the right product for standard HTTPS API calls. Traffic tunnels end to end, so the payload is never decrypted at the proxy. Bandwidth is bundled. No per-GB overage fees. Most Tray.io relay workloads are ordinary REST calls that fit comfortably in the Starter 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. Start with QuotaGuard Static direct at $19/month.

QuotaGuard Shield Pricing Starts at $29/Month

QuotaGuard Shield uses SSL passthrough, so QuotaGuard never decrypts your data. Reach for Shield direct at $29/month only when the relay carries regulated data and you need to meet HIPAA, PCI-DSS, or SOC 2 requirements. For standard Tray.io integrations, QuotaGuard Static is the correct pick.

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

Point Tray.io at the Relay and Ship

Deploy the relay once, set the HTTP Client connector to call its function URL with the two headers, and allowlist your subscription's two static IPs with the partner API. See the full pricing table at quotaguard.com/products/pricing. Grab the ready-to-run example from the lambda-relay repo and follow the QuotaGuard no-proxy relay guide to wire it up.