Instructor: So, the first part of the URL
is naturally the domain name.
The domain name should be either FQDN,
which is Fully Qualified Domain Name,
or a server name.
For example, in this URL taken from the eBay api,
you can see the FQDN, the Fully Qualified Domain Name.
In this case, it is api.ebay.com.
Now, what's important to note about a domain name is
that a protocol used should be HTTPS.
Using HTTP is outdated and unsecured,
and you should avoid it.
If you are using FQDN, Fully Qualified Domain Name,
then it should have an api in its name, like this.
So, you see here the protocol, which is HTTPS,
and the word api.
And then the other part of the domain name,
in this case myapp.com.
So, when including the api word in the domain name,
then the developer will be able to understand that
this domain is the correct place to go
when working with the api.
Okay, so let's start building a URL
which will be a best practice demonstrator using Beeceptor.
And if you will look at the URL in Beeceptor,
which is right here,
then you can see that using Beeceptor we have
a fully qualified domain name.
Although, we don't have full control of it,
so we don't have the word api in it.
My specific sub domain is called apicourse,
but again, you probably selected a different one.
So, we will start building the URL from this domain name.
And let's move on to the next lecture
to understand what comes right after the domain name.