Hi everyone!
I'm fairly new to Xano and currently exploring best practices for building core support functions such as authentication, versioning, security, and traceability.
Right now, my focus is on API versioning.
My goal is to offer consumers two versions of the same API endpoint:
GET /v1/users
GET /v2/users
The idea is to handle breaking changes in the response schema without forcing all consumers to immediately update their integrations. This approach prepares us for future updates—after all, it's easy to build, but hard to change later! 😅
I noticed that Xano allows renaming API groups after creation, but the result is that every endpoint gets grouped under "v1," which doesn't seem scalable or clear for our team over time.
Additionally, the branching feature doesn't appear to support launching two live branches simultaneously.
Has anyone faced a similar challenge? How did you handle API versioning in Xano? Any insights or tips would be greatly appreciated!
Best regards
Nicolas