Automate your digital signage fleet with the CloudyFy TV REST API
Every action in the CloudyFy TV dashboard, such as pairing a device, publishing a layout or pulling an uptime report, runs through a REST API you can call directly. It's the same API the dashboard itself uses, not a separate limited surface.
What is the CloudyFy TV API?
The CloudyFy TV API is a REST API at hub.cloudyfy.tv, backing 523 registered routes across the platform: devices, layouts, media, publishing, scheduling, analytics, reports, integrations, branding, and more. It's the same API the CloudyFy TV dashboard calls for every action, so nothing you can do in the CMS is unreachable from code.
This API matters most for two teams: an internal IT or ops group that wants to script fleet-wide changes instead of clicking through a dashboard one device at a time, and a systems integrator or reseller building their tooling on top of CloudyFy TV for their customers. Neither is boxed into a narrow "reporting-only" or "read-only" API surface, the same routes that power layout editing, publishing, and device pairing in the CMS are open to a script.
- JSON in, JSON out, over HTTPS
- Covers devices, layouts, media, playlists, schedules, publishing, analytics and proof-of-play, uptime reports, integrations, and branding
- No webhooks yet: automation today is request-driven, not event-driven
How do you authenticate and call the API?
Sign in
Authenticate with your CloudyFy TV account credentials, or SSO where configured, to get a short-lived access token and a longer-lived refresh token, the same tokens the dashboard's own session uses.Call an endpoint
Send the access token as a bearer token on any REST call your account has permission for. There's no separate developer API key today, so automation runs as a real user account, respecting that account's role and permissions.Refresh when it expires
The access token is short-lived; exchange your refresh token for a new one without asking the user to sign in again.Poll for changes
Since there are no webhooks, an integration checks for updates, new play events, device status, a completed report, by calling the relevant endpoint on your own schedule.
Why would you use the API instead of the dashboard?
Bulk operations
Pair, group, or reassign content across hundreds of devices in a script instead of clicking through each one.
Connect your own systems
Pull proof-of-play or uptime data into your own BI process, or push content updates from a system you already run, without a person in the loop.
Build on top of CloudyFy TV
A reseller or systems integrator can drive company and device management from their own tooling rather than the CMS.
Same permissions, same audit trail
API calls run as a real user under that user's role, so the same 34-module permission system and audit logging apply whether an action came from a click or a script.
What the API can't do yet
There is no separate developer API key or service account today; every call authenticates as a real user, so an integration needs a real login and inherits that user's permissions rather than a scoped machine credential. That means the practical setup for most integrations is a dedicated user account with a role scoped to exactly the modules the integration needs, not the account owner's own login. There are no webhooks: CloudyFy TV doesn't push events to your systems, so an integration has to poll. A full public API reference isn't published yet either; the internal specification only documents a fraction of the platform's routes and is being rebuilt.
What is behind the CloudyFy TV API?
The API isn't a thin layer bolted on for marketing purposes, it's the same interface the dashboard itself is built on, spanning 523 registered routes across the backend. That means device pairing, layout publishing, media upload with dedupe, schedule management, and the same uptime and proof-of-play reports available in the CMS are all reachable the same way.
FAQs
Put the CloudyFy TV API to work this week
Start on the free trial, or talk to us about the routes your integration needs.