screens:readScreens
Browse safe screen identity, presentation metadata, availability, and status.
Developers
Use a secure, read-only API to understand screens and effective playback state without depending on SignageWall's internal player or CMS contracts.
Deliberate access
Grant each integration only the resources it needs. Permissions are immutable, so rotation and permission changes remain explicit and auditable.
screens:readBrowse safe screen identity, presentation metadata, availability, and status.
playback:readResolve the effective, allowlisted content configuration for a known screen.
playlists:readRead playlist metadata and ordered content references.
media:readRead approved playback metadata and opaque public content locations.
Small, stable surface
Start with an organization-scoped credential, then request only the resource views your service needs. Every response is a Partner-owned projection designed to stay stable while SignageWall evolves behind it.
screens:read
playback:read
playlists:read
The configuration route is independently protected by playback:read.
Designed for production
The API exposes an explicit external model—not database records, arbitrary application configuration, or the internal player protocol.
Organization identity comes from the credential and is enforced in every resource query.
New internal fields stay private until they are deliberately added to a Partner mapper.
Run multiple credentials during migration, then revoke the previous credential without changing it.
HTTPS, Bearer-only authentication, identity quotas, no-store responses, and opaque URLs work together.
Partner API v1
Learn authentication, choose the right scopes, and make your first request in a few minutes.