Implemented today
- Workspace-scoped Platform management REST API: Library assets/groups and verified image/Lottie/WAV/MP3/MP4/PDF upload, Playlist drafts/immutable Ready versions, Channel/Location CRUD, Edge registration/archive, publication, Screen pairing/lifecycle and Schedule CRUD. Collection reads include pagination and supported filters.
- Offline-package export and download for eligible published content.
- Signed Platform event webhooks with delivery history.
- Four Queue REST endpoints for services, tickets, and live state.
- Outbound Queue ticket webhooks.
- Prayer schedule monthly Custom Push.
- Structured Widget Push v2 for Announcements, Today’s Schedule, Events, and Departure & Arrival.
- A Player-side Secure WebSocket protocol for compatible customer-operated relays.
Not part of the released Platform API
Layarva does not currently expose customer REST endpoints for:- Workspaces and membership.
- Screen Groups.
- Studio Design authoring or raw document/manifest ingestion.
- Human publishing approval review (the API can request review, not approve).
- Campaign management.
Uploads, offline packages and Platform webhooks
Follow the guides for MP3/MP4/PDF uploads, offline-package exports and signed Platform webhooks. If a request returns503, stop that workflow and retry later when instructed, or contact support with the response requestId. Do not repeatedly create jobs or subscriptions while the service is unavailable.
Queue ticket webhooks remain separate from Platform webhooks. PDF upload stores a document and does not make it a playable Playlist item. Ready, Publication success and offline-package readiness are not proof that a physical Screen imported or played the content.
Use only documented public routes for supported operations. Do not automate unsupported dashboard flows by copying private browser requests; internal contracts can change without public API versioning.
Custom HTML/JavaScript Widget APIs remain outside this documentation phase. Structured built-in Widgets use the supported Push and WebSocket contracts listed above.

