Netboxdemo NetBox API

Name: NetBox API
Brand: NetBox API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingbearer357 EndpointsREST

For Agents

Read and write NetBox 2.4 inventory: devices, IPs, VLANs, circuits, secrets, and tenancy on legacy installs.

Install Jentic One Beta

Connect the NetBox API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NetBox API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NetBox API.

Allocate, reserve, and release IP addresses and prefixes through the IPAM endpoints

Inventory devices, racks, and modules across one or many sites

Manage circuits and circuit terminations from upstream providers

GET STARTED

Start building with NetBox API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use NetBox API for, with concrete tasks.

★ Legacy NetBox 2.4 IP Allocation

Operators still running NetBox 2.4 use /ipam/prefixes/ and /ipam/ip-addresses/ to allocate IPs from a structured inventory rather than a wiki. The 2.4 spec lacks some 3.x-only fields, but the IPAM allocation endpoints behave the same way and slot into the existing Ansible or Terraform NetBox modules.

Reserve the next available /32 from prefix 10.20.0.0/24 in NetBox 2.4 and return the address record.

Inventory Reads on Legacy Installs

Teams that have not yet upgraded to NetBox 3.x use the 2.4 API to read device, rack, and circuit inventory from automation scripts. The /_choices/ endpoints expose the enum vocabulary for every model, which legacy 2.4 callers need because the full schema is not embedded in each list response.

List the valid status choices for the circuits model, then list every active circuit at site dc-east.

Tenant Source-of-Truth Reads

Multi-tenant environments use /tenancy/tenants/ to scope reads to one tenant on the 2.4 install. The endpoint returns tenant id, name, and group, which scripts then use to filter device, IP, and circuit reads to one customer's footprint.

List every tenant on the install and return the count of devices assigned to each.

AI Agent Integration via Jentic

An AI agent uses Jentic to call the NetBox 2.4 API on installs that have not yet upgraded. Jentic exposes the dcim, ipam, circuits, and tenancy operations by intent, so the same agent code can target either a 2.4 or 3.4 install by switching the spec it loads.

Use Jentic to search for allocate next available ip in netbox, load the 2.4 schema, and reserve the next /32 from prefix 10.20.0.0/24.

Key Endpoints

357 endpoints — this is the netbox 2.

METHOD

PATH

DESCRIPTION

GET

/circuits/circuits/

List provider circuits

GET

/circuits/circuit-terminations/

List circuit terminations

GET

/circuits/circuit-types/

List circuit type definitions

GET

/circuits/_choices/

List enum choices for the circuits model

GET

/circuits/circuits/{id}/

Get a circuit by id

GET

/circuits/circuits/

List provider circuits

GET

/circuits/circuit-terminations/

List circuit terminations

GET

/circuits/circuit-types/

List circuit type definitions

GET

/circuits/_choices/

List enum choices for the circuits model

GET

/circuits/circuits/{id}/

Get a circuit by id

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The NetBox 2.4 bearer token is stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access at execution time and the raw token never enters the agent context.

Intent-based discovery

Agents search Jentic by intent (for example, allocate an ip in netbox) and Jentic returns the matching 2.4 operation with its input schema, so the agent calls the right endpoint without traversing the spec by hand.

Time to first call

Direct NetBox 2.4 integration: 1 week for token handling, _choices lookups, and pagination across IPAM and DCIM. Through Jentic: under 1 hour to search, load, and execute.

FAQs

Specific to using NetBox API through Jentic.

What authentication does the NetBox 2.4 API use?

NetBox 2.4 uses bearer token authentication — generate a token in the NetBox UI under your user profile and pass it as Authorization: Token <key>. Jentic stores the token encrypted in the MAXsystem vault so it is injected at execution time rather than passed through the agent context.

How is this spec different from the NetBox 3.4 spec?

NetBox 2.4 has 357 endpoints versus 844 in 3.4. The 2.4 release includes the secrets module that was removed in 3.x, lacks the modules and journal entries added later, and uses /_choices/ endpoints to expose enum values rather than embedding them in each list response.

Can I allocate the next available IP from a NetBox 2.4 prefix?

Yes. /ipam/prefixes/ exposes an available-ips action that returns the next free address. Combine it with a write to /ipam/ip-addresses/ to allocate and assign the address. The behaviour is the same as in NetBox 3.x.

How do I list devices at a site on NetBox 2.4 through Jentic?

Search Jentic for list netbox devices at a site, load the 2.4 schema for the dcim devices endpoint, then execute with the site filter. The full flow is pip install jentic, search, load, execute.

What are the rate limits for the NetBox 2.4 API?

NetBox does not impose API rate limits in the spec — limits depend on the operator's deployment. Treat large list calls as paginated; on 2.4, the /_choices/ endpoints are cheap reads you can cache locally rather than refetching for every script run.

Should I use this spec or the netbox.dev/main spec?

Use this 2.4 spec only when targeting an install still on NetBox 2.4. For modern NetBox 3.4 deployments, use the netbox.dev/main or netbox.dev/netbox-api specs which cover the current model.