DemandFlow Support Centre

PROVIDER: Circuit Provider

The PROVIDER entity represents an ISP, telecom carrier, or circuit provider that delivers network connectivity services.

Default definition. This article describes the default PROVIDER 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 PROVIDER.

Entity properties

Property	Value
Entity code	`PROVIDER`
Display name	Circuit Provider
Plural	Circuit Providers
Level	42100
Extends	`COM`. See Entity Extension.

Use cases

PROVIDER represents an ISP, telecom carrier, or managed network service provider - distinct from VEN (hardware manufacturers/vendors). While a VEN sells you switches and routers, a PROVIDER sells you circuits, internet transit, MPLS VPNs, and dark fiber. Key fields include account number, NOC (Network Operations Centre) contact details for outage reporting, customer portal URL, and ASN. The related list shows LOGICALCONNECTION records delivered by this provider, giving a complete view of all circuits from a given carrier. This entity enables provider management: tracking SLA compliance, consolidating circuit costs, and planning provider diversity for resilience.

Fields

Because this entity extends COM, some fields may actually be stored on the linked base record rather than on this record directly. See Entity Extension.

General

Field	Type	Required	Notes
`name`	text	Yes	Provider Name.
`df_extendObject`	reference → `COM`		Parent company.
`description`	text (multi-line)		Description.
`accountNumber`	text		Account Number.
`asn`	reference → `ASN`		Provider ASN.
`status`	enum		Status. Valid ids: `1` (Active), `2` (Evaluating), `3` (Inactive).
`nocPhone`	text		NOC Phone.
`nocEmail`	text		NOC Email.
`salesContact`	reference → `PPL`		Sales Contact.
`techContact`	reference → `PPL`		Technical Contact.
`portalUrl`	text (URL)		Customer Portal.
`website`	text (URL)		Website.
`statusPageUrl`	text (URL)		Status Page.

Additional panels

Activity timeline panel attached.

Relationships

Lookups: df_extendObject points at COM record; asn points at ASN record; salesContact points at PPL record; techContact points at PPL record.
Extends: this entity extends COM. See Entity Extension.
Related lists: LOGICALCONNECTION via format SUB.

Creating a Circuit Provider via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "PROVIDER",
  "level":    42100,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "df_extendObject": "",
  "description": "Long description text.",
  "accountNumber": "Example text"
}

Listing PROVIDER records

# All circuit providers in your tenant
GET /v1/entities/PROVIDER/SUB

DemandFlow Support Centre

PROVIDER: Circuit Provider

PROVIDER: Circuit Provider

Entity properties

Use cases

Fields

Additional panels

Relationships

Creating a Circuit Provider via the API

Listing PROVIDER records

See also

Was this article helpful?