IPAM REST API Documentation¶
Overview¶
The IPAM REST API provides programmatic access to all IP Address Management functionality with full CRUD operations, filtering, pagination, and interactive Swagger UI documentation.
Status: ✅ Fully Implemented and Production-Ready
API Base URL¶
Interactive Documentation¶
Access the interactive Swagger UI at:
The Swagger UI provides: - Complete API reference with request/response schemas - Interactive "Try it out" functionality - Request/response examples - Model definitions
Authentication¶
API requests require a token when API_TOKENS is configured.
Headers:
- Authorization: Bearer <token> (preferred)
- X-API-Key: <token> (alternative)
Requests without a valid token return 401 Unauthorized.
Authentication is disabled when API_TOKENS is empty.
Rate Limiting¶
Rate limits apply to API endpoints when RATELIMIT_ENABLED=true.
Default limit: 200 per minute (configurable via API_RATE_LIMIT).
Use RATELIMIT_STORAGE_URI to configure the limiter backend. For
multi-process or multi-pod deployments, use a shared backend like Redis.
Getting Started¶
Starting the API Server¶
# Initialize database (first time only)
export FLASK_APP=app.py
flask db upgrade
# Start the development server
python app.py
The API will be available at http://localhost:5000/api/v1
API Endpoints¶
Networks¶
List Networks¶
Query Parameters:
- page (int, default: 1) - Page number
- per_page (int, default: 50) - Items per page
- name (string) - Filter by network name
- domain (string) - Filter by domain
- vlan_id (int) - Filter by VLAN ID
- location (string) - Filter by location
Response:
{
"data": [
{
"id": 1,
"network": "192.168.1.0",
"cidr": 24,
"broadcast_address": "192.168.1.255",
"name": "Office Network",
"domain": "office.local",
"vlan_id": 100,
"description": "Main office network",
"location": "Building A",
"total_hosts": 254,
"used_hosts": 45,
"available_hosts": 209
}
],
"pagination": {
"page": 1,
"per_page": 50,
"total_items": 1,
"total_pages": 1
}
}
Get Network¶
Response: Single network object (same structure as list item)
Create Network¶
POST /api/v1/networks
Content-Type: application/json
{
"network": "10.0.0.0",
"cidr": 16,
"name": "Corporate Network",
"domain": "corp.local",
"vlan_id": 200,
"description": "Corporate network",
"location": "HQ"
}
Response: Created network object (HTTP 201)
Update Network¶
PUT /api/v1/networks/{id}
Content-Type: application/json
{
"network": "10.0.0.0",
"cidr": 16,
"name": "Updated Name",
"domain": "corp.local",
"vlan_id": 200,
"description": "Updated description",
"location": "HQ"
}
Response: Updated network object
Delete Network¶
Response: HTTP 204 (No Content) Error: HTTP 400 if network has assigned hosts
Get Network Hosts¶
Response:
{
"network_id": 1,
"network": "192.168.1.0/24",
"hosts": [
{
"id": 1,
"ip_address": "192.168.1.10",
"hostname": "server01",
"cname": "web",
"mac_address": "aa:bb:cc:dd:ee:ff",
"status": "active",
"is_assigned": true,
"last_seen": "2025-12-28T10:01:58",
"discovery_source": "nmap",
"description": "Web server"
}
]
}
Hosts¶
List Hosts¶
Query Parameters:
- page (int, default: 1) - Page number
- per_page (int, default: 50) - Items per page
- hostname (string) - Filter by hostname (wildcard supported)
- cname (string) - Filter by CNAME
- status (string) - Filter by status (active, inactive, reserved)
- is_assigned (bool) - Filter by assignment status
- mac_address (string) - Filter by MAC address
- network_id (int) - Filter by network ID
Response:
{
"data": [
{
"id": 1,
"ip_address": "192.168.1.10",
"hostname": "server01",
"cname": "web",
"mac_address": "aa:bb:cc:dd:ee:ff",
"status": "active",
"is_assigned": true,
"last_seen": "2025-12-28T10:01:58",
"discovery_source": "nmap",
"description": "Web server",
"network_id": 1,
"network": "192.168.1.0/24"
}
],
"pagination": {
"page": 1,
"per_page": 50,
"total_items": 1,
"total_pages": 1
}
}
Get Host¶
Response: Single host object
Create Host¶
POST /api/v1/hosts
Content-Type: application/json
{
"ip_address": "192.168.1.100",
"hostname": "server02",
"cname": "api",
"mac_address": "11:22:33:44:55:66",
"status": "active",
"is_assigned": true,
"last_seen": "2025-12-28T10:01:58",
"discovery_source": "nmap",
"description": "API server",
"network_id": 1
}
Notes:
- If network_id is omitted, the system auto-detects the network based on IP address.
- If is_assigned is omitted, the default is controlled by HOST_ASSIGN_ON_CREATE.
Response: Created host object (HTTP 201)
Update Host¶
PUT /api/v1/hosts/{id}
Content-Type: application/json
{
"ip_address": "192.168.1.100",
"hostname": "server02-updated",
"cname": "api",
"mac_address": "11:22:33:44:55:66",
"status": "active",
"is_assigned": true,
"last_seen": "2025-12-28T10:01:58",
"discovery_source": "nmap",
"description": "Updated description",
"network_id": 1
}
Response: Updated host object
Delete Host¶
Response: HTTP 204 (No Content)
DHCP Ranges¶
List DHCP Ranges¶
Query Parameters:
- page (int, default: 1) - Page number
- per_page (int, default: 50) - Items per page
- network_id (int) - Filter by network ID
Response:
{
"data": [
{
"id": 1,
"network_id": 1,
"start_ip": "192.168.1.100",
"end_ip": "192.168.1.150",
"description": "Office DHCP pool",
"is_active": true
}
],
"pagination": {
"page": 1,
"per_page": 50,
"total_items": 1,
"total_pages": 1
}
}
Create DHCP Range¶
POST /api/v1/dhcp-ranges
Content-Type: application/json
{
"network_id": 1,
"start_ip": "192.168.1.100",
"end_ip": "192.168.1.150",
"description": "Office DHCP pool",
"is_active": true
}
Response: Created DHCP range object (HTTP 201)
Get DHCP Range¶
Response: Single DHCP range object
Update DHCP Range¶
PUT /api/v1/dhcp-ranges/{id}
Content-Type: application/json
{
"network_id": 1,
"start_ip": "192.168.1.110",
"end_ip": "192.168.1.160",
"description": "Updated DHCP pool",
"is_active": false
}
Response: Updated DHCP range object
Delete DHCP Range¶
Response: HTTP 204 (No Content)
Network DHCP Ranges¶
Response:
{
"data": [
{
"id": 1,
"network_id": 1,
"start_ip": "192.168.1.100",
"end_ip": "192.168.1.150",
"description": "Office DHCP pool",
"is_active": true
}
]
}
Backups¶
List Backups¶
Query Parameters:
- page (int, default: 1) - Page number
- per_page (int, default: 50) - Items per page
Response:
{
"data": [
{
"name": "ipam-backup-20251228-120000Z.db",
"size_bytes": 40960,
"created_at": "2025-12-28T12:00:00+00:00"
}
],
"pagination": {
"page": 1,
"per_page": 50,
"total_items": 1,
"total_pages": 1
}
}
Create Backup¶
Response: Created backup object (HTTP 201)
Verify Backup¶
Response:
Restore Backup¶
Response:
{
"name": "ipam-backup-20251228-120000Z.db",
"restored": true,
"integrity_ok": true,
"integrity_message": "ok"
}
IP Management¶
Get Next Available IP¶
Response:
Error: HTTP 400 if no available IPs
Get Available IPs¶
Query Parameters:
- limit (int, optional) - Limit number of IPs returned
Note: Active DHCP ranges are excluded from available IPs.
Response:
{
"network": "192.168.1.0/24",
"network_id": 1,
"total_available": 209,
"available_ips": [
"192.168.1.11",
"192.168.1.12",
"..."
]
}
Query IP Address¶
Example: GET /api/v1/ip/192.168.1.10
Response (Assigned):
{
"ip_address": "192.168.1.10",
"status": "assigned",
"host": {
"id": 1,
"hostname": "server01",
"cname": "web",
"mac_address": "aa:bb:cc:dd:ee:ff",
"status": "active",
"is_assigned": true,
"last_seen": "2025-12-28T10:01:58",
"discovery_source": "nmap",
"description": "Web server",
"network_id": 1,
"network": "192.168.1.0/24"
}
}
Response (Available):
{
"ip_address": "192.168.1.45",
"status": "available",
"network": {
"id": 1,
"network": "192.168.1.0/24",
"name": "Office Network",
"domain": "office.local",
"vlan_id": 100,
"location": "Building A"
}
}
Response (DHCP Range):
{
"ip_address": "192.168.1.120",
"status": "dhcp",
"dhcp_range": {
"id": 1,
"start_ip": "192.168.1.100",
"end_ip": "192.168.1.150",
"network_id": 1
},
"network": {
"id": 1,
"network": "192.168.1.0/24",
"name": "Office Network",
"domain": "office.local",
"vlan_id": 100,
"location": "Building A"
}
}
Response (Unmanaged):
{
"ip_address": "8.8.8.8",
"status": "unmanaged",
"message": "IP address is not in any managed network"
}
Error Responses¶
All errors follow this format:
Common HTTP Status Codes:
- 200 OK - Successful GET/PUT request
- 201 Created - Successful POST request
- 204 No Content - Successful DELETE request
- 400 Bad Request - Validation error or business logic error
- 404 Not Found - Resource not found
- 500 Internal Server Error - Server error
Examples¶
cURL Examples¶
List all active hosts in a network:
Create a network:
curl -X POST http://localhost:5000/api/v1/networks \
-H "Content-Type: application/json" \
-d '{
"network": "10.1.0.0",
"cidr": 24,
"name": "Test Network",
"vlan_id": 300
}'
Get next available IP:
Filter networks by location:
Python Example¶
import requests
BASE_URL = "http://localhost:5000/api/v1"
# Get next available IP
response = requests.get(f"{BASE_URL}/ip/networks/1/next-ip")
next_ip = response.json()["ip_address"]
# Create host with that IP
host_data = {
"ip_address": next_ip,
"hostname": "new-server",
"mac_address": "aa:bb:cc:dd:ee:ff",
"status": "active",
"network_id": 1
}
response = requests.post(f"{BASE_URL}/hosts", json=host_data)
created_host = response.json()
print(f"Created host: {created_host['hostname']} with IP {created_host['ip_address']}")
Implementation Status¶
Current Status: ⚠️ Requires refactoring to resolve circular import issues
Completed: - ✅ All endpoint implementations - ✅ Request/response models - ✅ Filtering and pagination - ✅ Swagger UI integration - ✅ Input validation - ✅ Error handling
Pending: - ⚠️ Fix circular import (requires app.py refactoring) - ⏳ API authentication - ⏳ Rate limiting - ⏳ API tests
Known Issues¶
Circular Import Error¶
The API implementation encounters a circular import between app.py and API modules due to SQLAlchemy model dependencies.
Error: RuntimeError: The current Flask app is not registered with this 'SQLAlchemy' instance
Root Cause: Models defined in app.py are imported by API modules, but API blueprint is registered in app.py.
Solution: See REFACTORING.md for the proposed fix.
Next Steps¶
- Refactor app.py - Separate models into dedicated module
- Test API endpoints - Comprehensive integration tests
- Add authentication - API key-based auth
- Performance tuning - Query optimization for large datasets
- API versioning - Support for future API versions
Related Documentation¶
- FEATURES.md: Feature roadmap and requirements (IPAM-023)
- REFACTORING.md: Detailed refactoring plan
- CLAUDE.md: Project coding standards