API design versioning with multiple databases -

Should there be a setup version for the API database for the API URL?

The API starts with Api.domain.com/v1/ and eventually for api.domain.com/v2/ .

Is it good practice to setup different databases for each API version?

  will use the api.domain.com/v1/ database api_v1 api.domain.com/v2/ will use the database api_v2    
 
 
 You probably have data similar to API access, so I think it is very impossible to use two databases. An API should always be the underlying business logic and database to be refined so that changes in an API reflect the possibility of negotiating business logic. The API version is a good thing, but to avoid big problems in the future, there should be a good estimate of what and what will definitely change in the future.