Features The API

Let the building decide what the screen says

The interesting content is already in your systems. It should not need a person to copy it onto a wall.

Available on signage plans.

REST over the things that matter

Screens, scenes, widgets and schedules are all addressable. Create a scene, move a widget, assign it to a screen or change tomorrow's schedule — from a script, from your booking system, or from whatever already knows the answer.

Keys are per-account and revocable, and every call is attributable to the key that made it.

  • Screens, scenes, widgets and schedules over REST
  • Per-key access, revocable independently
  • Bulk-friendly: a hundred dishes need not be a hundred requests

Webhooks for live values

For numbers that change often — a queue length, a production count, a room's next booking — a webhook widget takes a POST and shows what it is given. No polling, no integration to build on our side, and the value arrives on the wall by the same path everything else does.

Where people use it

Room booking

The panel outside each room shows what your booking system already knows.

A factory line

Output against target, posted by the system that counts it, on a board everyone can see.

Questions

Is the API included?

It is a plan feature; the documentation in the portal shows exactly what each key can reach.

Do I need to poll for changes?

No. Post a value to a webhook widget and the screen showing it updates.

Can a key be limited to one screen?

Keys are scoped and revocable, so an integration that only drives reception need not be able to touch the boardroom.

Put it on the wall

Start free on one screen. No card until you add a second.