How can we handle versioning of APIs created with Backendless and also Multi-tenancy based data segregation?

How can we handle versioning of APIs created with Backendless and also Multi-tenancy based data segregation?

Are you talking about the built-in APIs or the API Services you deploy into Cloud Code?

The API’s which we write/create in backendless.

Since the name of an API service in a backendless app must be unique (even across different deployment models), it is recommended to add a version identifier to the service name, for example WeatherServiceV1, WeatherServiceV2, etc.