1
00:00:00,240 --> 00:00:02,913
Instructor: And the next part is the version.

2
00:00:03,900 --> 00:00:06,510
Now we are going to have a long discussion

3
00:00:06,510 --> 00:00:08,460
about versioning later in this course,

4
00:00:08,460 --> 00:00:10,650
but it is important to understand

5
00:00:10,650 --> 00:00:13,860
where the version part comes in the URL.

6
00:00:13,860 --> 00:00:17,610
So, if the version strategy we are using is URL,

7
00:00:17,610 --> 00:00:20,910
and again, we will talk about version strategies later,

8
00:00:20,910 --> 00:00:22,797
then the version comes now.

9
00:00:22,797 --> 00:00:26,430
And the version should come only as natural number,

10
00:00:26,430 --> 00:00:30,480
meaning it should be positive and no decimals.

11
00:00:30,480 --> 00:00:33,060
In addition, the version could be prefixed

12
00:00:33,060 --> 00:00:35,280
with the little v.

13
00:00:35,280 --> 00:00:38,171
So, it can be something like this.

14
00:00:38,171 --> 00:00:41,880
So, you see here the domain name, the API word,

15
00:00:41,880 --> 00:00:43,473
and the version.

16
00:00:44,310 --> 00:00:47,853
So, let's see how it is implemented using Beeceptor.

17
00:00:49,140 --> 00:00:52,190
So, here is Beeceptor exactly where we left it

18
00:00:52,190 --> 00:00:53,610
in the last lecture,

19
00:00:53,610 --> 00:00:58,153
and all we need to do now is add a / and v1.

20
00:00:59,460 --> 00:01:01,410
So, by adding the v1,

21
00:01:01,410 --> 00:01:03,420
we notify the developer

22
00:01:03,420 --> 00:01:05,730
that the API version he is going to use

23
00:01:05,730 --> 00:01:08,313
is the first version of the API.

24
00:01:09,480 --> 00:01:12,011
So, again, don't click the Save Rule,

25
00:01:12,011 --> 00:01:14,220
leave the page as it is,

26
00:01:14,220 --> 00:01:17,073
and you will come back to it in the next lecture.