Viridi · Schema
EntityView
A JSON object representing the entity view.
CompanyEnergyEnergy StorageBatteryIoTIndustrial IoTEnergy ManagementManufacturingTelematicsMicrogrid
Properties
| Name | Type | Description |
|---|---|---|
| entityId | object | JSON object with the referenced Entity Id (Device or Asset). |
| tenantId | object | JSON object with Tenant Id. |
| customerId | object | JSON object with Customer Id. Use 'assignEntityViewToCustomer' to change the Customer Id. |
| name | string | Entity View name |
| type | string | Device Profile Name |
| keys | object | Set of telemetry and attribute keys to expose via Entity View. |
| startTimeMs | integer | Represents the start time of the interval that is used to limit access to target device telemetry. Customer will not be able to see entity telemetry that is outside the specified interval; |
| endTimeMs | integer | Represents the end time of the interval that is used to limit access to target device telemetry. Customer will not be able to see entity telemetry that is outside the specified interval; |
| id | object | JSON object with the Entity View Id. Specify this field to update the Entity View. Referencing non-existing Entity View Id will cause error. Omit this field to create new Entity View. |
| createdTime | integer | Timestamp of the Entity View creation, in milliseconds |
| additionalInfo | object | Additional parameters of the device |
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-entity-view-schema.json",
"title": "EntityView",
"description": "A JSON object representing the entity view.",
"x-generated": "2026-10-20",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/viridi-parente-entity-view-controller-api-openapi.yml#/components/schemas/EntityView",
"properties": {
"entityId": {
"$ref": "#/$defs/EntityId",
"description": "JSON object with the referenced Entity Id (Device or Asset)."
},
"tenantId": {
"$ref": "#/$defs/TenantId",
"description": "JSON object with Tenant Id.",
"readOnly": true
},
"customerId": {
"$ref": "#/$defs/CustomerId",
"description": "JSON object with Customer Id. Use 'assignEntityViewToCustomer' to change the Customer Id.",
"readOnly": true
},
"name": {
"type": "string",
"description": "Entity View name"
},
"type": {
"type": "string",
"description": "Device Profile Name"
},
"keys": {
"$ref": "#/$defs/TelemetryEntityView",
"description": "Set of telemetry and attribute keys to expose via Entity View."
},
"startTimeMs": {
"type": "integer",
"format": "int64",
"description": "Represents the start time of the interval that is used to limit access to target device telemetry. Customer will not be able to see entity telemetry that is outside the specified interval;"
},
"endTimeMs": {
"type": "integer",
"format": "int64",
"description": "Represents the end time of the interval that is used to limit access to target device telemetry. Customer will not be able to see entity telemetry that is outside the specified interval;"
},
"id": {
"$ref": "#/$defs/EntityViewId",
"description": "JSON object with the Entity View Id. Specify this field to update the Entity View. Referencing non-existing Entity View Id will cause error. Omit this field to create new Entity View."
},
"createdTime": {
"type": "integer",
"format": "int64",
"description": "Timestamp of the Entity View creation, in milliseconds",
"readOnly": true
},
"additionalInfo": {
"$ref": "#/$defs/JsonNode",
"description": "Additional parameters of the device"
}
},
"required": [
"entityId",
"name",
"type"
],
"$defs": {
"AttributesEntityView": {
"properties": {
"cs": {
"type": "array",
"description": "List of client-side attribute keys to expose",
"items": {
"type": "string"
}
},
"ss": {
"type": "array",
"description": "List of server-side attribute keys to expose",
"items": {
"type": "string"
}
},
"sh": {
"type": "array",
"description": "List of shared attribute keys to expose",
"items": {
"type": "string"
}
}
},
"required": [
"cs",
"sh",
"ss"
]
},
"CustomerId": {
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "ID of the entity, time-based UUID v1"
},
"entityType": {
"type": "string",
"description": "string",
"enum": [
"CUSTOMER"
]
}
},
"required": [
"entityType",
"id"
]
},
"EntityId": {
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "ID of the entity, time-based UUID v1"
},
"entityType": {
"type": "string",
"enum": [
"TENANT",
"CUSTOMER",
"USER",
"DASHBOARD",
"ASSET",
"DEVICE",
"ALARM",
"RULE_CHAIN",
"RULE_NODE",
"ROLE",
"ENTITY_VIEW",
"WIDGETS_BUNDLE",
"WIDGET_TYPE",
"TENANT_PROFILE",
"DEVICE_PROFILE",
"ASSET_PROFILE",
"API_USAGE_STATE",
"TB_RESOURCE",
"OTA_PACKAGE",
"EDGE",
"RPC",
"QUEUE",
"NOTIFICATION_TARGET",
"NOTIFICATION_TEMPLATE",
"NOTIFICATION_REQUEST",
"NOTIFICATION",
"NOTIFICATION_RULE",
"QUEUE_STATS"
]
}
},
"required": [
"entityType",
"id"
]
},
"EntityViewId": {
"properties": {
"id": {
"type": "string",
"format": "uuid",
"description": "ID of the entity, time-based UUID v1"
},
"entityType": {
"type": "string",
"description": "string",
"enum": [
"ENTITY_VIEW"
]
}
},
"required": [
"entityType",
"id"
]
},
"JsonNode": {
"description": "A value representing the any type (object or primitive)"
},
"TelemetryEntityView": {
"properties": {
"timeseries": {
"type": "array",
"description": "List of time-series data keys to expose",
"items": {
"type": "string"
}
},
"attributes": {
"$ref": "#/$defs/AttributesEntityView",
"description": "JSON object with attributes to expose"
}
},
"required": [
"attributes",
"timeseries"
]
},
"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-entity-view"
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.