If you called the Screenly API directly with an API token, rather than through the dashboard, to create or update a screen, create a shared playlist, or send a workspace invitation, your request could be rejected with an authentication error even though the token was valid. The underlying check only recognized dashboard session tokens, not regular API tokens. Requests authenticated with a valid API token now succeed as expected.
Improvements
- Applied security updates to third-party dependencies across several of our services.
