What is an endpoint?

Question

I read about OAuth, and he continues to talk about endpoints. What is an endpoint?

Answer 1

All the answers posted so far are correct, the endpoint is just one end of the communication channel. In the case of OAuth, you need to have three endpoints:

• Temporary Mandate Request URL (called the request name URL in the OAuth 1.0a community specification). This is the URI to which you send the request to receive an unauthorized request token from the server / service provider.
• Resource owner authorization URL (called the user authorization URL in the OAuth 1.0a community specification). This is the URI that you instruct the user to authorize the request token obtained from the temporary credential URI.
• Token request URI (called the access token URL in the OAuth 1.0a community specification). This is the URI to which you send a request to exchange an authorized request token for an access token, which you can then use to gain access to a protected resource.

Hope that helps sort it out. Have fun learning about OAuth! Ask more questions if you have difficulty implementing the OAuth client.

Answer 2

Come on guys :) We could make it simpler with examples:

/this-is-an-endpoint /another/endpoint /some/other/endpoint /login /accounts /cart/items 

and when it is placed under the domain, it will look like this:

 https://example.com/this-is-an-endpoint https://example.com/another/endpoint https://example.com/some/other/endpoint https://example.com/login https://example.com/accounts https://example.com/cart/items 

It can be either http or https, we use https in the example.

Also, the endpoint may differ for different HTTP methods, for example:

 GET /item/{id} PUT /item/{id} 

- two different endpoints: one for r etrieving (as in the abbreviation c R ud "), and the other for u pdating (as in" cr U d ")

And that’s all really that simple!

Answer 3

This is one end of the communication channel, so often it will appear as the URL of a server or service.

Answer 4

An endpoint is a URL pattern used to communicate with an API.

Answer 5

The endpoint in the OpenID authentication jargon is the URL to which you send (POST) the authentication request.

Excerpts from the Google Authentication API

To get the Google OpenID endpoint, perform a discovery by sending an HTTP GET or HEAD request to https://www.google.com/accounts/o8/id . When using GET, we recommend setting the Accept header to "application / xrds + xml". Google returns an XRDS document containing the URL of the OpenID provider endpoint. The endpoint address is marked as:

 <Service priority="0"> <Type>http://specs.openid.net/auth/2.0/server</Type> <URI>{Google login endpoint URI}</URI> </Service> 

After you have acquired the Google endpoint, you can send authentication requests to it by specifying the appropriate parameters (available on the linked page). You connect to the endpoint by sending a request to a URL or by sending an HTTP POST request.

Answer 6

An endpoint is a connection point for a service, tool, or application that is accessed over a network. In the software world, any application that works and listens for connections uses the endpoint as the front door. When you want to connect to an application / service / tool for exchanging data, you connect to its endpoint

Answer 7

The term endpoint was originally used for WCF services. Later, although the word is used synonymously with API resources, REST recommends invoking these URIs (URIs [which] understand HTTP verbs and following the REST architecture) as “Resource”.

In short, a resource or endpoint is an entry point to a remotely hosted application that allows users to communicate with it through the HTTP protocol.

Answer 8

The terminus of a term is a URL that focuses on creating a request. Take a look at the following examples from different perspectives:

 /api/groups/6/workings/1 /api/v2/groups/5/workings/2 /api/workings/3 

They can clearly refer to the same source in this API.

Answer 9

A negative vote (s) has nothing to do with me, but the source (: there is not even a reason for this is indicated.

---

Each endpoint is a location from which APIs can access the resources necessary to perform their functions. That is, the place where the API sends requests and where the resource lives is called the endpoint.

From a good source .