Authenticate to the Samsung MagicINFO Server Open API and push scheduled content plus manage device groups/tags
domain: docs.samsungvx.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST credentials to the MagicINFO authentication endpoint to obtain a time-sensitive api_token
Include the api_token header on all subsequent /restapi/v1.0 calls
Upload content and move it through the approve/publish workflow before it can be scheduled
Create or update device groups and tags/categories so displays can be targeted collectively
Create/update a schedule (program) that assigns approved content to a device group with start/end times
Re-authenticate for a fresh api_token once the current one expires, since MagicINFO tokens are time-limited
Known gotchas
Content must be explicitly approved before it is schedulable — a schedule referencing unapproved content is rejected rather than queued for later
Open API endpoints and versions (v1.0 vs v2.0) differ across MagicINFO Server 6/8/9 releases, so scripts written against one server's Swagger doc can silently 404 on a different installed version
Device-group membership changes don't retroactively apply to already-running schedules — a device added to a group after schedule assignment must have the schedule reassigned to pick it up
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?