SignageWallDevelopers

Partner API v1

Build with SignageWall

Read screens, playlists, media, and effective playback state through a secure API designed for long-lived server integrations.

Start the quickstart Explore API reference

What you can build

The Partner API gives external platforms a compact, tenant-safe view of a SignageWall organization without exposing the CMS, player protocol, or storage implementation.

Screen inventory Discover presentation-ready screen metadata and status. Effective playback Resolve the exact, safe content presentation for a screen. Content catalog Read ordered playlists and approved media metadata. Security by default Use immutable scopes, isolated tenants, and opaque URLs.

Your first request

Create a credential in CMS → Developers, place it in a server-side secret manager, and send it only in the Bearer authorization header.

bash 
export SIGNAGEWALL_API_BASE="https://api.signagewall.com/api/partner/v1"
export SIGNAGEWALL_PARTNER_API_KEY="<credential>"

curl --request GET \
  --url "$SIGNAGEWALL_API_BASE/organization" \
  --header "Authorization: Bearer $SIGNAGEWALL_PARTNER_API_KEY" \
  --header "Accept: application/json"

Designed to stay stable

Partner API v1 owns its schemas. Changes to database documents, CMS responses, applications, and the player protocol do not automatically change this contract.

  • Every response is built through explicit, default-deny field mapping.
  • Every data query is constrained to the credential organization.
  • Scopes remain independent and immutable for the lifetime of a credential.
  • Media URLs are opaque locations; clients do not depend on their host or storage shape.