Manage IP address space (IPAM) for an ISP using the NetBox REST API

domain: netboxlabs.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Generate a token in NetBox (v2 tokens on NetBox 4.5+, prefixed nbt_) and send it as Authorization: Bearer nbt_<key>.<token> on every request; older Authorization: Token <token> v1 tokens are deprecated and removed entirely in NetBox 5.0.
  2. Manage IP address space with GET/POST on /api/ipam/prefixes/ and /api/ipam/ip-addresses/, assigning an IP to a device/VM interface via its assigned_object_type (e.g. dcim.interface) and assigned_object_id.
  3. Manage related infrastructure objects as needed — /api/ipam/vlans/, /api/dcim/devices/, /api/dcim/sites/, /api/dcim/racks/ — using the same token and base API path.
  4. Filter and trim responses with query params like ?device_id=, ?ordering=-created, ?fields=id,name,status, or ?omit=..., and always include the trailing slash on detail endpoints or you'll get a redirect instead of the object.
  5. Paginate large result sets with ?limit=&offset= (default cap 1000 unless raised), or use ?limit=0 only when you deliberately want to fetch an entire table in one request.

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans