assign an updated playlist to a group of pisignage players and deploy it via the rest api
domain: piathome.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate against the pisignage server to obtain an access token (valid for 4 hours, reused across subsequent api calls)
Use the swagger UI at piathome.com/apidocs to find and test the playlist and group endpoints and their exact payload shapes
Create or update a playlist and add/reorder assets in it via the playlists endpoints
Assign the playlist to a group and set its schedule (start/end date, time window, recurrence)
Trigger a deploy on the group so the staged playlist/schedule is pushed to its players — content is staged and not live until deploy runs
Poll the group/player status endpoints to confirm the deploy succeeded
Known gotchas
All content changes are staged (draft) and are NOT sent to players until an explicit deploy action is called — a very common integration bug is forgetting the deploy step
The auth token expires after 4 hours, so long-running integrations must re-authenticate periodically
The interactive/swagger API docs live on a separate domain (piathome.com/apidocs) from the main product documentation (pisignage.com/doc), and the swagger schema has gaps in some parameter descriptions
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?