Correct way to version a asp.net WebApi

Question

I am just about to go live with an api that I wrote using the new webapi.

I want to futureproof via some kind of versioning for the api - meaning if a client starts using the api straight after release I don't want them to have to go back and update their code with any changes I may make.

I can think of a couple of ways of applying a versions.

//myapi.com/foo?bar=1234&v1
//myapi.com/v1/foo?bar=1234

What are most people doing? I want to follow best practises but I also want the api to be clean to manage.

Suggestions are most welcome :)

Community · Accepted Answer · 2017-05-23 10:28:57Z

2

Web API is nothing like another way to write RESTful services. Please to this thread for more details Best practices for API versioning?

edited May 23, 2017 at 10:28

CommunityBot

11 silver badge

answered Sep 3, 2012 at 7:29

petro.sidlovskyy

5,1032 gold badges27 silver badges29 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Correct way to version a asp.net WebApi

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related