TL;DR: On October 1, 2026, we’re switching off API v3 (api.screenlyapp.com/api/v3/*) for good. Everything moves to API v4.1, the faster, more secure, more capable API that already powers the Screenly dashboard, our devices, the CLI, and our MCP server. If you’re still on v3, now’s the time to migrate. The good news: v4.1 isn’t a replacement, it’s an upgrade you’ll actually enjoy.
Why we’re doing this
At Screenly, we’ve always believed in doing fewer things exceptionally well. Running two API generations side by side is the opposite of that. v3 served us well for years, but it was built on an older architecture that no longer matches how we build, or how you build.
API v4.1 is a ground-up rethink, and it’s simply better in every dimension that matters.
A modern architecture
v4.1 is built on PostgREST, giving you direct, efficient access to your data with capabilities v3 could never offer. Filter on any field, even nested ones, with a single query (GET /v4/assets?type=eq.video). Embed related resources in one call instead of five (GET /v4/playlists?select=*,playlist_items(*)). Fewer round trips, less glue code, faster integrations.
Battle-tested every day
This isn’t a new API we’re asking you to gamble on. v4.1 is the same API our own web dashboard and devices run on. Every screen update, every playlist change, every sync across our fleet goes through v4.1, which means it’s exercised at production scale, around the clock. When you build on v4.1, you’re building on exactly what we build on.
Security by design, not by add-on
Security is the foundation of everything we do at Screenly, and that applies to our API surface too. Every legacy stack we keep running is extra surface to defend. By consolidating on v4.1, all of our security hardening, auditing, and monitoring effort goes into one modern codebase, built from day one around our zero-trust philosophy. A smaller, sharper attack surface is a win for every customer.
Stability you can depend on
Consolidating on a single, modern API stack means we can move faster on reliability, monitoring, and performance for everyone. Every hour we don’t spend maintaining legacy infrastructure is an hour spent making the platform you rely on even more solid.
One ecosystem
v4.1 is also where the rest of our developer tooling lives: the Screenly CLI, Edge Apps, and our MCP server for AI assistants like Claude and Cursor are all built on it. Migrating puts your integrations on the same foundation as everything else.
What happens on October 1, 2026
All v3 endpoints will stop responding.
Requests to api.screenlyapp.com/api/v3/* will return an error.
There is no partial shutdown or grace mode, so please treat this as a hard deadline.
How to migrate
- Audit your integrations.
Search your codebase forapi/v3endpoints. - Reuse your existing API token, or generate a fresh one from your workspace security settings (
https://{your-workspace}.screenlyapp.com/manage/workspace/settings/security).
Your tokens work with v4.1 too. - Move to v4.1 endpoints.
Our API v4.1 documentation covers authentication, endpoints, and object attributes with copy-paste examples in cURL, Python, JavaScript, Ruby, Go, and more. - Consider skipping raw HTTP entirely.
For many workflows, the Screenly CLI or MCP server gets you there faster. - Test before the deadline.
v4.1 is live today, so you can migrate and verify at your own pace, right now.
Most migrations take hours, not weeks, and you’ll likely end up with less code than you started with.
We’re here to help
Stuck on a v3 pattern you can’t map to v4.1? Reach out via our support center and we’ll help you find the v4.1 way. There always is one, and it’s usually nicer.
Thanks for building with us!
