Documentation +
Getting Started5
AI Agents4
App Builders1
Languages8
Platforms11
Popular Guides5
Utilities1
Getting Started5
AI Agents4
App Builders1
Languages8
Platforms11
Popular Guides5
Utilities1

Static IP guide

Making API requests with a static IP from a Node app on Netlify

Netlify Functions run as regional Node.js functions, and like most serverless compute, each invocation can land on a different outbound IP. Store your Fixie proxy URL as an environment variable scoped to the Functions context, and axios routes every call from a fixed pair of addresses instead of whatever address that invocation happened to get.

RuntimeNode.js and JavaScript
PlatformNetlify
DestinationAPI allowlisting
Fixie productFixie HTTP/S proxy

Recommended setup

Use Fixie HTTP/S proxy for HTTP and HTTPS requests to an API, webhook provider, or service that allowlists outbound IP addresses. Store the proxy value in FIXIE_URL, then configure Node.js to route outbound traffic through Fixie before connecting to API allowlisting.

Set up Fixie on Netlify

Create a Fixie HTTP/S proxy in the Fixie dashboard. Copy the proxy value into Netlify environment variables as FIXIE_URL, and copy the outbound IPs into the destination allowlist.

Implementation

The example below shows the core application-side change. Keep credentials in environment variables and avoid committing proxy, database, or API secrets.

Make an HTTP request through FIXIE_URL

const axios = require('axios');

const fixieUrl = new URL(process.env.FIXIE_URL);

axios.get('https://api.example.com/data', {
  proxy: {
    protocol: 'http',
    host: fixieUrl.hostname,
    // URL drops default ports, so fall back to 80 for Fixie's standard proxy port.
    port: Number(fixieUrl.port) || 80,
    auth: {
      username: fixieUrl.username,
      password: fixieUrl.password,
    },
  },
}).then((response) => {
  console.log(response.status);
});

Good to know

  • Scope the variable to the production context (or per-branch, for preview deploys) so a staging Fixie proxy never leaks into production logs.
  • Setting it from the CLI looks like netlify env:set FIXIE_URL "<proxy-url>" --context production, which keeps the value out of the repo.
  • A change to an environment variable does not take effect until the next deploy, so trigger one after adding FIXIE_URL for the first time.

Allowlist and test the static IPs

  1. Open the Fixie dashboard and copy the outbound IP addresses for this proxy.
  2. Add both IPs to the API provider.
  3. Deploy the updated Node.js app on Netlify.
  4. Run a small connection test before sending production traffic.

Related guides

Related docs

Is this guide useful?