publish media and playlists to a player via the signagelive network api
domain: build.signagelive.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request Network API access by submitting Signagelive's partner sign-up form — credentials are issued after review, not self-service
Develop and test against Signagelive's separate development environment (distinct URLs, clients, and licenses) before moving to production
Authorize your application against a specific customer Network — this is an app-to-network grant, not tied to an individual user, and your app must provide a UI flow for the customer to grant it
Use the Network API (a RESTful API mirroring the Signagelive UI) to upload media, create/edit playlists, and publish content to players
Optionally use the separate Web Triggers API to fire interactive on-screen events, or the Proof-of-Play API to retrieve playback logs
Known gotchas
The Network API is partner-gated: there is no public self-serve API key — access requires signing up and being onboarded by Signagelive
Production and development environments use different client apps and credentials; dev clients will not connect to production and vice versa
Detailed endpoint-level reference docs are shared with approved partners during onboarding rather than published in full on the public build.signagelive.com site
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?