How do I add an IP address?

Requires Basic

Quick answer

Open the Network module, stay on the IP Addresses tab, and click “Add IP Address”. Only the address itself is required — all other fields (subnet mask, gateway, DNS name, VLAN, status, assigned asset) are optional. If left blank, the status defaults to Available.

Prerequisites

The Network module is part of the core and available in all plans from Basic onward; there is no separate quantity limit for IP addresses.

Open the “Network” module. Choose Network in the left-hand navigation. The IP Addresses tab is already active. At the top is the “Add IP Address” button.

Screenshot pending netzwerk-ip-01 The 'IP Addresses' tab in the Network module with the 'Add IP Address' button

The 'IP Addresses' tab with the 'Add IP Address' button.
Fill in the form. Enter at least the address (e.g. 10.0.0.1). Optional but recommended:
- Subnet mask — e.g. 255.255.255.0
- Gateway — e.g. 10.0.0.254
- DNS name — e.g. srv-fileserver.intern
- VLAN ID — chosen from your VLANs
- Status — Available (default), Assigned, Reserved, or Deprecated
- Assigned asset — the device using the address
- Description
Screenshot pending netzwerk-ip-02 The 'Add IP Address' form with the fields Address, Subnet Mask, Gateway, DNS Name, VLAN, Status

The form for a new IP address. Only the address is required.
Save. The address appears in the list immediately, sorted by address. Use the row menu to edit or delete it later.

The same action via the REST API: a POST to /api/v1/network/ips with a bearer token (scope write). Only address is required.

curl -X POST https://demo.notory.io/api/v1/network/ips \
  -H "Authorization: Bearer inv_dein_token" \
  -H "Content-Type: application/json" \
  -d '{
    "address": "10.0.0.10",
    "subnet_mask": "255.255.255.0",
    "gateway": "10.0.0.254",
    "dns_name": "srv-fileserver.intern",
    "status": "reserved",
    "description": "Reserviert fuer neuen Fileserver"
  }'

On success, the API responds with HTTP 201 Created:

{
  "id": "0190f3a2-6c11-7b8e-9f2a-1c4d5e6f7a80",
  "tenant_id": "3d9b0c12-4e5a-4f88-b1c7-2a9e6d4f0011",
  "address": "10.0.0.10",
  "subnet_mask": "255.255.255.0",
  "gateway": "10.0.0.254",
  "vlan_id": null,
  "dns_name": "srv-fileserver.intern",
  "status": "reserved",
  "assigned_asset_id": null,
  "description": "Reserviert fuer neuen Fileserver",
  "created_at": "2026-07-08T09:20:00Z",
  "updated_at": "2026-07-08T09:20:00Z"
}

To change it, use PUT /api/v1/network/ips/{id} (only the fields you send are overwritten); to delete it, use DELETE /api/v1/network/ips/{id} (administrator only).

Possible errors: 401 (token missing/invalid), 403 (no write access, or no administrator role when deleting), 422 (validation — e.g. empty address or unknown status).

What happens behind the scenes?

Tenant assignment: The address is assigned to your current tenant (tenant_id) and is invisible to other tenants.
Audit trail: Notory internally records the creator and last editor (created_by/updated_by) along with timestamps — the IP address is the only network object that keeps this user trail.
Default status: Without input, status = Available applies. The status is purely documentation and controls how the address appears in lists and in the search for free IPs.
No uniqueness check: Notory does not enforce a unique rule on the address and does not automatically detect duplicate assignments. The same IP can technically be entered more than once — use the status field (Available/Assigned/Reserved) consistently to keep occupancy under control.
Links stay stable: If the assigned asset or the linked VLAN is later deleted, Notory sets the link to null (SET NULL) — the IP address itself is retained.