Skip to content

Lock internal AI endpoints to approved IP and CIDR ranges

Ensure B2B partner integrations and internal admin pipelines only accept traffic from static VPN, VPC NAT, or enterprise IP blocks.

Copy the prompt and paste it into the AI assistant you already use.

Checklist for clean IP allowlist rules

  1. 01

    Verify static NAT egress first

    Confirm your serverless or VPC functions route via static NAT IPs before turning on strict blocks.

  2. 02

    Bind allowlists per key when multi-tenant

    Apply IP restrictions per enterprise API key rather than breaking mobile users on shared endpoints.

  3. 03

    Label CIDR entries clearly

    Tag every whitelisted range with the office, staging cluster, or partner name for future audits.

  4. 04

    Pair IP checks with secret keys

    Treat CIDR rules as an extra network layer alongside bearer tokens—never as standalone auth.

Common questions

Can different B2B customers each set their own allowed IP list?

Yes. Per-key IP allowlists restrict each enterprise key to its own NAT IPs without impacting other tenants.

What happens if an allowed key is leaked and run from a stranger's laptop?

Requests from outside the approved CIDR range are dropped at the edge with HTTP 403 before execution.

Does APIkit support IPv6 CIDR notation?

Yes, both IPv4 and IPv6 addresses and CIDR subnet masks are supported in allowlist configurations.