curl --request POST \
--url https://api2.rhombussystems.com/api/report/getCustomEventsReport \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '
{
"deviceFacetUuids": [
"AAAAAAAAAAAAAAAAAAAAAA.v0"
],
"endTimeMs": 1640998800000,
"extendedResponse": true,
"locationUuid": "AAAAAAAAAAAAAAAAAAAAAA",
"promptUuid": "AAAAAAAAAAAAAAAAAAAAAA",
"startTimeMs": 1640995200000
}
'{
"error": true,
"errorMsg": "<string>",
"timeSeriesDataPoints": [
{
"deviceFacetUuid": "AAAAAAAAAAAAAAAAAAAAAA.v0",
"events": [
{
"checkCondition": true,
"image": "<string>",
"imageOffsets": [
123
],
"prompt": "<string>",
"timestampMs": 123,
"value": "<string>"
}
],
"promptUuid": "AAAAAAAAAAAAAAAAAAAAAA"
}
],
"warningMsg": "<string>"
}Retrieves a custom events report containing raw time-series event values recorded by selected prompts and devices within the specified time window. The report can be filtered by: • promptUuid – The specific prompt to query. • deviceFacetUuids – A set of devices to include. • locationUuid – The location context for the query. For example, a request may specify a promptUuid to fetch results from a certain LLM prompt, and additionally restrict results to only devices in a given locationUuid. The time range (startTimeMs → endTimeMs) is required and determines the interval of events returned. The response includes, per device and prompt, the raw event values (numeric or boolean as string) along with timestamps, check-condition results (if selected), and prompt type.
curl --request POST \
--url https://api2.rhombussystems.com/api/report/getCustomEventsReport \
--header 'Content-Type: application/json' \
--header 'x-auth-apikey: <api-key>' \
--header 'x-auth-scheme: <x-auth-scheme>' \
--data '
{
"deviceFacetUuids": [
"AAAAAAAAAAAAAAAAAAAAAA.v0"
],
"endTimeMs": 1640998800000,
"extendedResponse": true,
"locationUuid": "AAAAAAAAAAAAAAAAAAAAAA",
"promptUuid": "AAAAAAAAAAAAAAAAAAAAAA",
"startTimeMs": 1640995200000
}
'{
"error": true,
"errorMsg": "<string>",
"timeSeriesDataPoints": [
{
"deviceFacetUuid": "AAAAAAAAAAAAAAAAAAAAAA.v0",
"events": [
{
"checkCondition": true,
"image": "<string>",
"imageOffsets": [
123
],
"prompt": "<string>",
"timestampMs": 123,
"value": "<string>"
}
],
"promptUuid": "AAAAAAAAAAAAAAAAAAAAAA"
}
],
"warningMsg": "<string>"
}Documentation Index
Fetch the complete documentation index at: https://api-docs.rhombus.community/llms.txt
Use this file to discover all available pages before exploring further.
Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).
Authentication scheme identifier. Use api-token for standard API key authentication, partner-api-token for partner API key authentication. Must be paired with the x-auth-apikey header containing your API key.
api-token, api, partner-api-token, partner-api Request object for custom LLM reports.
Uuids of the selected devices
RUUID with optional appended facet information
"AAAAAAAAAAAAAAAAAAAAAA.v0"
The end timestamp (in Unix epoch milliseconds) of the selected interval
1640998800000
base 64 (url-safe) uuid string
"AAAAAAAAAAAAAAAAAAAAAA"
base 64 (url-safe) uuid string
"AAAAAAAAAAAAAAAAAAAAAA"
The start timestamp (in Unix epoch milliseconds) of the selected interval
1640995200000
Was this page helpful?