How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Viridi Rule Chain Controller API

The rule-chain-controller API from Viridi — 19 operation(s) for rule-chain-controller.

Viridi Rule Chain Controller API is one of 56 APIs that Viridi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include rule-chain-controller. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 22 operations across 19 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 3.7.0.

Requests are made against a single base URL, https://vista.viridiparente.com.

22 operations 19 paths 14 schemas 3 DELETE10 GET9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.7.0
Base URL
https://vista.viridiparente.com
Authentication
HTTP Loginpassword
Resource Areas
1

Authentication & Security 1

Viridi Rule Chain Controller API declares 1 security scheme for authenticating requests. It uses HTTP loginpassword authentication (HTTP_login_form).

  • HTTP_login_form — Enter Username / Password

Paths & Operations 22

Across 19 paths, the API surfaces 22 operations — 3 DELETE, 10 GET, 9 POST. Each is listed below with its method, path, parameters, and response codes.

rule-chain-controller 22
POST
/api/ruleChains/import
Import Rule Chains
importRuleChains 1 param body → 200
POST
/api/ruleChain
Create Or Update Rule Chain (saveRuleChain)
saveRuleChain body → 200
POST
/api/ruleChain/{ruleChainId}/root
Set Root Rule Chain (setRootRuleChain)
setRootRuleChain 1 param → 200
POST
/api/ruleChain/{ruleChainId}/edgeTemplateRoot
Set Edge Template Root Rule Chain (setEdgeTemplateRootRuleChain)
setEdgeTemplateRootRuleChain 1 param → 200
POST
/api/ruleChain/{ruleChainId}/autoAssignToEdge
Set Auto Assign To Edge Rule Chain (setAutoAssignToEdgeRuleChain)
setAutoAssignToEdgeRuleChain 1 param → 200
DELETE
/api/ruleChain/{ruleChainId}/autoAssignToEdge
Unset Auto Assign To Edge Rule Chain (unsetAutoAssignToEdgeRuleChain)
unsetAutoAssignToEdgeRuleChain 1 param → 200
POST
/api/ruleChain/testScript
Test Script function
testScript 1 param body → 200
POST
/api/ruleChain/metadata
Update Rule Chain Metadata
saveRuleChainMetaData 1 param body → 200
POST
/api/ruleChain/device/default
Create Default Rule Chain
saveRuleChain_1 body → 200
POST
/api/edge/{edgeId}/ruleChain/{ruleChainId}
Assign rule chain to edge (assignRuleChainToEdge)
assignRuleChainToEdge 2 params → 200
DELETE
/api/edge/{edgeId}/ruleChain/{ruleChainId}
Unassign rule chain from edge (unassignRuleChainFromEdge)
unassignRuleChainFromEdge 2 params → 200
GET
/api/ruleNode/{ruleNodeId}/debugIn
Get latest input message (getLatestRuleNodeDebugInput)
getLatestRuleNodeDebugInput 1 param → 200
GET
/api/ruleChains
Get Rule Chains (getRuleChains)
getRuleChains 6 params → 200
GET
/api/ruleChains/export
Export Rule Chains
exportRuleChains 1 param → 200
GET
/api/ruleChain/{ruleChainId}
Get Rule Chain (getRuleChainById)
getRuleChainById 1 param → 200
DELETE
/api/ruleChain/{ruleChainId}
Delete rule chain (deleteRuleChain)
deleteRuleChain 1 param → 200
GET
/api/ruleChain/{ruleChainId}/output/labels
Get Rule Chain output labels (getRuleChainOutputLabels)
getRuleChainOutputLabels 1 param → 200
GET
/api/ruleChain/{ruleChainId}/output/labels/usage
Get output labels usage (getRuleChainOutputLabelsUsage)
getRuleChainOutputLabelsUsage 1 param → 200
GET
/api/ruleChain/{ruleChainId}/metadata
Get Rule Chain (getRuleChainById)
getRuleChainMetaData 1 param → 200
GET
/api/ruleChain/tbelEnabled
Is TBEL script executor enabled
isTbelEnabled → 200
GET
/api/ruleChain/autoAssignToEdgeRuleChains
Get Auto Assign To Edge Rule Chains (getAutoAssignToEdgeRuleChains)
getAutoAssignToEdgeRuleChains → 200
GET
/api/edge/{edgeId}/ruleChains
Get Edge Rule Chains (getEdgeRuleChains)
getEdgeRuleChains 6 params → 200

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are RuleNode (12 properties), RuleChain (10 properties), RuleChainOutputLabelsUsage (5 properties), RuleChainMetaData (5 properties). Each schema is shown below with its type and property counts.

RuleNodeId
object
2 properties 2 required
RuleChainId
object
2 properties 2 required
RuleChain
object
A JSON value representing the rule chain.
10 properties 2 required
RuleChainData
object
A JSON value representing the rule chains.
2 properties 2 required
PageDataRuleChain
object
4 properties
JsonNode
A value representing the any type (object or primitive)
DefaultRuleChainCreateRequest
object
A JSON value representing the request.
1 property 1 required
RuleChainOutputLabelsUsage
object
5 properties 5 required
NodeConnectionInfo
object
3 properties 3 required
RuleNode
object
12 properties
RuleChainImportResult
object
4 properties
RuleChainMetaData
object
A JSON value representing the rule chain metadata.
5 properties 5 required
TenantId
object
2 properties 2 required
RuleChainConnectionInfo
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

viridi-parente-rule-chain-controller-api-openapi.yml Raw ↑

Other APIs Viridi publishes across the network.

Viridi Admin Controller API
Viridi Alarm Comment Controller API
Viridi Alarm Controller API
Viridi Asset Controller API
Viridi Asset Profile Controller API
Viridi Audit Log Controller API
Viridi Auth Controller API
Viridi Cbrs Controller API
Viridi Component Descriptor Controller API
Viridi Customer Controller API
Viridi Dashboard Controller API
Viridi Device Connectivity Controller API
Where this information came from

This is an independent, third-party profile of Viridi Rule Chain Controller API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.