Static IP Delivery

Static IP delivery routes your outbound webhook deliveries through a dedicated proxy server with a fixed egress IP address. This lets your destination servers whitelist a single IP, meeting strict firewall and compliance requirements.

How It Works

When static IP delivery is enabled, webhooks flow through a dedicated relay proxy instead of being delivered directly from Cloudflare's edge network:

Webhook Received → Cloudflare Edge → Static IP Proxy → Your Destination
                                      (fixed IP)

Without static IP delivery, webhooks are sent directly from Cloudflare Workers, which use a large pool of shared egress IPs that can change at any time. With static IP enabled, all deliveries exit from a single, predictable IP address that you can add to your firewall allowlist.

Availability

Static IP delivery is available on Pro and Business plans. It is enabled by default for all destinations and webhook endpoints on qualifying plans.

Plan	Static IP Available
Free	No
Starter	No
Pro	Yes
Business	Yes

TIP

Upgrade to a Pro or Business plan to access static IP delivery. See Plans & Limits for details.

Configuration

Static IP delivery is controlled per destination (inbound webhooks) and per webhook endpoint (outbound webhooks) via the useStaticIp field. It defaults to enabled (true) on qualifying plans.

Destinations

Create a destination with static IP disabled

curl -X POST "https://api.hookbase.app/api/destinations" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Internal Service",
    "slug": "internal",
    "url": "https://api.example.com/webhooks",
    "useStaticIp": false
  }'

Enable static IP on an existing destination

curl -X PATCH "https://api.hookbase.app/api/destinations/{destinationId}" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "useStaticIp": true
  }'

Webhook Endpoints

Create an endpoint with static IP disabled

curl -X POST "https://api.hookbase.app/api/webhook-endpoints" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Partner API",
    "url": "https://partner.example.com/hooks",
    "useStaticIp": false
  }'

Enable static IP on an existing endpoint

curl -X PATCH "https://api.hookbase.app/api/webhook-endpoints/{endpointId}" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "useStaticIp": true
  }'

Via Dashboard

1. Navigate to Destinations or Webhook Endpoints
2. Click Add or edit an existing resource
3. Toggle Static IP Delivery on or off
4. Save your changes

Finding Your Static IP

Your organization's static IP address is displayed in the Hookbase dashboard under Settings → Static IP. Provide this IP to your network team or destination service for firewall whitelisting.

Use Cases

Financial Services

Banks and payment processors often require all incoming traffic to originate from pre-approved IP addresses. Static IP delivery satisfies this requirement without complex VPN setups.

Healthcare Systems

HIPAA-regulated systems may require IP-based access controls as part of their security posture. Static IP ensures webhook deliveries come from a known address.

Enterprise Networks

Large organizations with strict perimeter firewalls can whitelist the Hookbase static IP instead of opening access to Cloudflare's full IP range.

Best Practices

• Use static IP only when required — Direct delivery is faster since it skips the relay proxy. Only enable static IP for destinations that require IP whitelisting.
• Combine with other security — Static IP is one layer. Pair it with signature verification, IP filtering, and HTTPS for defense in depth.
• Keep firewall rules updated — If Hookbase changes its static IP (rare, with advance notice), update your firewall rules promptly.
• Disable for internal services — If your destination doesn't require IP whitelisting, disable static IP to reduce latency.

Limitations

• Plan requirement — Only available on Pro and Business plans. Deliveries on Free and Starter plans always use direct delivery.
• Slight added latency — Routing through the relay proxy adds a small amount of latency compared to direct delivery (typically under 50ms).
• HTTP destinations only — Static IP applies to HTTP webhook deliveries. Warehouse destinations (S3, R2, GCS) are not routed through the relay.

Related

• IP Filtering — Restrict which IPs can send webhooks to your sources
• Plans & Limits — Plan tiers and feature availability
• Destinations — Configure webhook delivery targets