# Creating OAuth Endpoints
This guide will you implement the two endpoints required for OAuth 2.0 with the Authorization Code Flow, `/authorize` and `/oauth/token`. We'll also go over some OAuth concepts to make it as easy as possible.
## Terminology
* **Resource Owner** **(Door Locks Account Owner):** The person, installer, company or end-user who owns the door locks or can grant access to a building. This person will sign in to your server.
* **Resource/Authorization Server (Your Server)**: The server granting access to the door locks, that's what we're creating here!
* **Client (Seam)**: Application requesting access to the door locks on behalf of the Door Locks Account Owner. This is Seam! We're a client requesting access on behalf of the door locks owner, so that the door locks owner can get delivery services.
{% hint style="info" %}
If you use an external authorization provider like Auth0 or Clerk, you'll have a separate Resource and Authorization server. We can handle this! Contact `integrations@getseam.com`
{% endhint %}
## Endpoints
### Overview
* **/authorize** - This endpoint provides a web page for the Door Locks Account Owner to sign into
* **/oauth/token** - Client (Seam) calls this after the user signs in
### GET /authorize
This endpoint can return the HTML for a webpage for a user to sign into (expand this box to see an example!). You can use your own internal endpoints to validate the user, then, using your database, create an authorization code that we'll use in a later step. The authorization code just represents that a user successfully logged in. It can be a UUID or a random string. To avoid storing codes in your database, you may consider using a signed JWT for the authorization code.\
\
It is very important that you validate that the `redirect_uri` goes to `*.integrations.getseam.com`, or a malicious actor could gain access to your system by redirecting the Door Locks Account Owner to their domain.
## Provide a webpage for the Door Locks Account Owner to sign into
`GET` `https://devicecloud.example.com/authorize`
#### Query Parameters
| Name | Type | Description |
| ----------------------------------------------- | ------ | ---------------------------------------------------- |
| redirect\_uri\* | String | URL to redirect Intercom Owner to after they sign in |
{% tabs %}
{% tab title="200: OK Return a login web page" %}
```javascript
email:
password:
```
{% endtab %}
{% endtabs %}
### POST /oauth/token
Seam sends you an Authorization code it got from `/authorize`, as well as a Client ID of "seam" and Client Secret, which we will provide you. While testing your login flow, you can use "seamsecret" as your Client Secret.
You should return an Access Token, which can be a long random string, UUID, or signed JWT. You'll use this access token to allow seam to access Devices and Access Codes.
Seam will attach the access token in it's `Authorization` header like so: `Authorization: Bearer `
## Exchange an Authorization Code for an Access Token
`POST` `https://devicecloud.example.com/oauth/token`
#### Request Body
| Name | Type | Description |
| ------------------------------------------------ | ------ | ---------------------------------- |
| code\* | String | Authorization code from /authorize |
| client\_id\* | String | The client\_id should be "seam" |
| client\_secret\* | String | A secret provided to you by Seam. |
{% tabs %}
{% tab title="200: OK " %}
```javascript
{
"access_token": "MODojXFjngsV8Z2xAymEi5CdCTo9ZpQf4tXTLO2L061ae"
}
```
{% endtab %}
{% endtabs %}
## Resources
* [Auth0 Authorization Code Flow documentation](https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow)