SVC: Service
A network service instance running on a device, binding IP addresses to protocols and ports.
SVC definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches SVC.Entity properties
| Property | Value |
|---|---|
| Entity code | SVC |
| Display name | Service |
| Plural | Services |
| Level | 42400 |
Use cases
A network service instance running on a device, binding IP addresses to protocols and ports.
SVC represents a specific network service running on a device - for example, HTTP on port 443, SSH on port 22, or DNS on port 53. It binds together a device (COMPINV), one or more IP addresses (IPADDRESS), a protocol (TCP/UDP/SCTP), and port number(s). This is distinct from NSRV which is a high-level business service catalogue entry. SVC is the device-level implementation: 'this server runs HTTPS on 10.0.1.5:443'. It enables dependency mapping (which services run where), security auditing (what ports are open), and impact analysis (if this device fails, which services are affected).
Fields
Service Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | e.g., HTTP, SSH, DNS, NTP, SNMP |
description | text (multi-line) | Description. | |
protocol | enum | Yes | Valid ids: 1 (TCP), 2 (UDP), 3 (SCTP), 4 (TCP+UDP). |
ports | text | Yes | Single port, range, or list (e.g., 443, 8080-8090, 80,443) |
status | enum | Valid ids: 1 (Active), 2 (Planned), 3 (Disabled). |
Assignment
| Field | Type | Required | Notes |
|---|---|---|---|
device | reference → COMPINV | Device this service runs on | |
ipAddresses | array of references → IPADDRESS | IP addresses this service listens on |
Relationships
- Lookups:
devicepoints at aCOMPINVrecord;ipAddressespoints at multipleIPADDRESSrecord.
Creating a Service via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SVC",
"level": 42400,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"protocol": 1,
"ports": "Example ports"
}Listing Services
GET /v1/entities/SVC/SUB