Signage

Control-center API for Raspberry Pi digital signage. Devices never host this service.

This API is the only place screens, pages, publishing, pairing, and device identity are managed. Operator user types: admin, area-manager, manager, member (from Directory memberships for service signage). Raspberry Pi players use display_device (actorId is the device id). locationId on a screen is an opaque id from the calling site.

Device loop

A Pi enrolls itself. It cannot choose an account or screen.

1. POST /v1/devices/enroll
2. An operator claims it with the pairing code and assigns a screen
3. Publish a page to that screen
4. The device polls POST /v1/device/sync and fetches assets by SHA-256

Device routes use /v1/device/* and /v1/devices/* (singular and plural prefixes).

What it does not own

• Rendering on the Pi (the device client)
• Marketing site CMS
• Venue operations

See the Signage API reference.