Viridi · Schema
RuleChain
A JSON value representing the rule chain.
CompanyEnergyEnergy StorageBatteryIoTIndustrial IoTEnergy ManagementManufacturingTelematicsMicrogrid
Properties
| Name | Type | Description |
|---|---|---|
| id | object | JSON object with the Rule Chain Id. Specify this field to update the Rule Chain. Referencing non-existing Rule Chain Id will cause error. Omit this field to create new rule chain. |
| createdTime | integer | Timestamp of the rule chain creation, in milliseconds |
| tenantId | object | JSON object with Tenant Id. |
| name | string | Rule Chain name |
| type | string | Rule Chain type. 'EDGE' rule chains are processing messages on the edge devices only. |
| firstRuleNodeId | object | JSON object with Rule Chain Id. Pointer to the first rule node that should receive all messages pushed to this rule chain. |
| root | boolean | Indicates root rule chain. The root rule chain process messages from all devices and entities by default. User may configure default rule chain per device profile. |
| debugMode | boolean | Reserved for future usage. |
| configuration | object | |
| additionalInfo | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/viridi-parente/main/json-schema/viridi-parente-rule-chain-schema.json",
"title": "RuleChain",
"description": "A JSON value representing the rule chain.",
"x-generated": "2026-10-20",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/viridi-parente-rule-chain-controller-api-openapi.yml#/components/schemas/RuleChain",
"properties": {
"id": {
"$ref": "#/$defs/RuleChainId",
"description": "JSON object with the Rule Chain Id. Specify this field to update the Rule Chain. Referencing non-existing Rule Chain Id will cause error. Omit this field to create new rule chain."
},
"createdTime": {
"type": "integer",
"format": "int64",
"description": "Timestamp of the rule chain creation, in milliseconds",
"readOnly": true
},
"tenantId": {
"$ref": "#/$defs/TenantId",
"description": "JSON object with Tenant Id.",
"readOnly": true
},
"name": {
"type": "string",
"description": "Rule Chain name"
},
"type": {
"type": "string",
"description": "Rule Chain type. 'EDGE' rule chains are processing messages on the edge devices only.",
"enum": [
"CORE",
"EDGE"
]
},
"firstRuleNodeId": {
"$ref": "#/$defs/RuleNodeId",
"description": "JSON object with Rule Chain Id. Pointer to the first rule node that should receive all messages pushed to this rule chain."
},
"root": {
"type": "boolean",
"description": "Indicates root rule chain. The root rule chain process messages from all devices and entities by default. User may configure default rule chain per device profile."
},
"debugMode": {
"type": "boolean",
"description": "Reserved for future usage."
},
"configuration": {
"$ref": "#/$defs/JsonNode"
},
"additionalInfo": {
"$ref": "#/$defs/JsonNode"
}
},
"required": [
"name",
"tenantId"
],
"$defs": {
"JsonNode": {
"description": "A value representing the any type (object or primitive)"
},
"RuleChainId": {
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "ID of the entity, time-based UUID v1"
},
"entityType": {
"type": "string",
"description": "string",
"enum": [
"RULE_CHAIN"
]
}
},
"required": [
"entityType",
"id"
]
},
"RuleNodeId": {
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "ID of the entity, time-based UUID v1"
},
"entityType": {
"type": "string",
"description": "string",
"enum": [
"RULE_NODE"
]
}
},
"required": [
"entityType",
"id"
]
},
"TenantId": {
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "ID of the entity, time-based UUID v1"
},
"entityType": {
"type": "string",
"description": "string",
"enum": [
"TENANT"
]
}
},
"required": [
"entityType",
"id"
]
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/viridi-parente-rule-chain"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.