The user-based API refers to Chevereto API V4 and will enable new ways for interacting with Chevereto as it begins to evolve into a headless API which will enable to programmatically do everything Chevereto related like image uploading, managing albums, configuring settings and more.

What it means

Every single action in the system will be available under this HTTP API, enabling anyone to build rich Chevereto-based applications by leveraging backend on Chevereto’s and creating tailored user interfaces for your very own needs.

Will enable us to ship features early as the system gets headless, from there can build your own UI and leverage the API to do everything Chevereto related.

Power users will be able to craft their own UI, with early access to features enabling to stand out from the crowd.

Chevere

Chevereto's user-based API is being built on top of the Chevere library, my own high-quality PHP library which after 6 years under development is finally stable to fulfill its original purpose as the backbone of next gen Chevereto software.

For Chevereto we can expect an extensible routing system thanks to Router, with HTTP Controller and Schwager API standard for a self-documented API.

Development

Chevereto is massive and this feature must be implemented progressively during V4.1’s lifecycle. It means that the API will be getting new endpoints in patch releases.

User-based API will start rolling from V4.1.0 with the most wanted endpoints first (image upload, management, etc) and the goal is to mirror the current internal API during the 4.X cycle.

This new feature won’t affect the current public API at /api or the internal API at /json because the user-based API is being made from scratch, it is a different piece of software that I will magically wire with the old system. You don’t need to worry a thing.