So in this video, we're going to talk about the pros and cons of each each different ways of applying
API version.
We have talked about three ways.
We have the versioning applying the header.
We have commercially applied through the vault and we have versioning applied through the URL.
Right.
All of them are pretty easy provided that we download that you get package that I showed earlier.
But I personally like like I said before, I like the way in the header letter just because different
versions of the API has different has the consistent endpoints.
But that may be a problem for you if you want to use a different type of your file for each different
versions, just because it's very clear which endpoint you're heading.
Right.
You can even test that invoice with your browser.
You don't have to use a tool like Posman to post a header.
So in that case, that is truly the most convenient way for you, right?
Same with the query stream.
It's in the URL, right.
It has the same benefits as having the version in the rot.
The problem was having the version in.
The question is that you may have tons of questions in that URL already.
And developers who use it will probably think that's a little bit messy, very prone to mistakes, because
there could be tons of your questions and they may forget about adding the version number and then hitting
the relevant number.
So in one word, it's really just up to you, up to your business decisions, your development shops,
decisions, whichever way works for you, the best is the best.