Create and schedule a remote/live DataSet in Xibo CMS via the API so a Ticker/Table widget pulls dynamic JSON or CSV data on a refresh interval
domain: account.xibosignage.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate via OAuth2 client credentials against the CMS API
POST /api/dataset to create a new DataSet, then POST /api/dataset/{id}/column to define columns matching the remote source's fields
PUT /api/dataset/{id} with dataSetSource=remote, uri, method, and postData to point at the external JSON/CSV endpoint
Set refreshRate and clearRate/truncateOnEmpty to control how often the CMS re-polls the source and whether stale rows are purged
Assign the DataSet to a Ticker or Table widget on a Layout via the playlist/widget endpoint
GET /api/dataset/{id}/data to verify ingestion before relying on it in a live schedule
Known gotchas
Remote DataSets are pulled by the CMS server, not the player, so the server (not the display) needs outbound network access to the remote URI; an unreachable source leaves stale cached rows without erroring
Columns must be mapped at creation time; if the remote source's schema changes later, unmapped fields are silently dropped rather than auto-added
refreshRate is capped by the server's own cron/task-runner frequency (commonly ~1 minute), so true sub-minute refresh is not achievable via remote DataSets
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?