Skip to content

IP allowlists

An IP allowlist limits which client addresses may use your data. There are two kinds of list:

ListApplies toWho changes it
OrganizationEvery API key, and the console’s query, import and export toolsOwners and admins
Per keyOne API keyOwners, admins and developers

A list with no entries allows every address. When both lists have entries, a request must match both: a key’s list narrows the organization’s, it never widens it.

Where it is enforced

  • HTTP, MCP and Bolt on db.namidb.com, before anything else runs. A Bolt session is re-checked on every statement, so an open connection is cut off as soon as its address stops being allowed.
  • The console’s query editor, importer and export downloads, against the address of the person using the console.
  • Management API export requests and downloads.

A refused request answers 403 ip_not_allowed. The message names the address that was seen and which list refused it. Over Bolt it is a Neo.ClientError.Security.Forbidden failure and the connection closes.

Adding entries

Console: API keys → IP allowlist for the organization’s list, or the IP allowlist button on a key’s row for its own list. Each entry is an IPv4 or IPv6 address or CIDR range with an optional label:

203.0.113.7 one address (stored as 203.0.113.7/32)
203.0.113.0/24 a range
2001:db8:1234::/48 an IPv6 range

Ranges are normalised (203.0.113.7/24 is stored as 203.0.113.0/24), and /0 is refused. With the API:

Terminal window
curl -X POST https://app.namidb.com/api/v1/ip-allowlist \
-H "Authorization: Bearer $NAMIDB_MANAGEMENT_TOKEN" -H "Content-Type: application/json" \
-d '{"cidr": "203.0.113.0/24", "label": "office"}'
# A key's own list:
curl -X POST https://app.namidb.com/api/v1/ip-allowlist \
-H "Authorization: Bearer $NAMIDB_MANAGEMENT_TOKEN" -H "Content-Type: application/json" \
-d '{"cidr": "198.51.100.10", "label": "ci runner", "api_key_id": "8f14e45f-…"}'
PlanEntries per list
Free1
Pro20
Scale100

After a downgrade, longer lists keep being enforced; you just can’t add more until they fit.

Behaviour to know

  • Changes reach every endpoint within about two seconds, including open Bolt sessions.
  • Rotating a key keeps its allowlist.
  • Changes need the second factor when you have one enrolled, and are in the audit log.
  • Add your own address (and your CI runners’) before turning on an organization list, or your console queries will be refused too.
  • Requests refused by an allowlist are not counted as usage.

Finding the right address

The address NamiDB sees is the public address your traffic leaves from: your office’s or VPN’s egress, a NAT gateway, or your cloud provider’s outbound range. ip_not_allowed messages name it. Serverless platforms often use large, changing address pools; prefer key scoping and short expiry there.