Docs
Core API overview
The Zonecast core API serves management routes under /v1. Your installation publishes OpenAPI at /openapi.json.
Management routes live under /v1 on your core API. Authenticate them with the account API key. The running server publishes Swagger at /docs/ and the machine-readable spec at /openapi.json. Those paths are on the API origin, not on this website.
Schedules, campaigns, announcements, catalogs, and device sync use the same operations as the dashboard. Read the current resource before a PUT: programming routes replace a complete calendar or schedule list.
- Authentication for the Bearer token.
- Schedules and announcements for rotation, volume, and exact-time payloads.
Account, search, and sync
Core routes are account-local. A standalone installation has one fixed account. Zonecast Cloud resolves the account through the proprietary control service. Read GET /v1/account for identity and audio defaults. GET /v1/search searches management resources. Player sync uses a device token, not the account key: GET /v1/sync/{syncId}.
Programming PUT routes replace a complete calendar, audience list, or schedule list. Read the current resource before editing a subset. The machine-readable spec for the running server is GET /openapi.json.
The core API, dashboard, website, storage worker, and shared packages use the MIT license. See self-hosting for a standalone install, and device sync for pairing.