.NET Core API versioning using header with "v" as prefix in version number

Viewed 13

Versioning is implemented in my .NET Core API using header "api-version=1.0" and everything working fine. Now, team wants to change the header value to "v1.0". I see all recommendations to use version number format as major.minor.[status] with status as optional (ex: Beta, RC). I didn't come across any suggestions to use "v1.0". Can you please let us know whether it is a good practice to use character prefix before version number?

If we go with this route, I think DefaultApiVersion, MapToApiVersion etc will not work without adding extensions to parse & remove "v" in the version number.Thanks for your time.

0 Answers
Related