Integrate with Dub
Learn how to set up Dub OAuth applications to authenticate users with OAuth 2.0.
Integrations allow you to extend the capabilities of Dub and seamlessly connect with third-party platforms and services.
In this guide, you will learn how to create and manage integrations on Dub, allowing you to incorporate Dub’s link management infrastructure into your application.
Integrating via OAuth 2.0 (recommended)
Dub supports OAuth 2.0 authentication, which is recommended if you build integrations extending Dub’s functionality.
We recommend you use a OAuth client library to integrate the OAuth flow. You can find recommended libraries in a variety of programming languages here.
Set up OAuth 2.0
Here is a step-by-step guide on how to set up OAuth 2.0 authentication with Dub.
Create an OAuth2 application in Dub
- Go to the OAuth Apps tab in your workspace.
- Click on Create OAuth App.
- Fill in the required fields to create an OAuth2 application.
Redirect users to authorization URL
When you want to authenticate a user, you need to redirect them to the Dub OAuth authorization URL.
Parameters:
Property | Description |
---|---|
client_id | The client ID of your OAuth application. |
redirect_uri | The URL to redirect the user to after they authorize the application. Make sure this URL is registered in your OAuth application. |
response_type | Expected response type. It should be code . |
scope | A space separated list of scopes that you want to request access to. Read more about scopes here. |
state | The state parameter to prevent against CSRF attacks. Read more about it here |
An example URL would look like this:
Exchange code for an access token
The code
parameter is returned in the query string when the user is redirected back to your application. You can exchange this code for an access token by making a POST request to the Dub OAuth token URL.
The Content-Type
header should be set to application/x-www-form-urlencoded
.
Parameters:
Property | Description |
---|---|
code | The code you received when the user was redirected back to your application. |
client_id | The client ID of your OAuth application. |
client_secret | The client secret of your OAuth application. |
redirect_uri | The same redirect URI you used in the authorization URL. |
grant_type | The grant type. It should be authorization_code . |
Response:
After a successful request, you will receive a JSON response with the access token.
We recommend using the PKCE flow for native desktop or mobile application or a single-page app (SPA) where the client_secret
cannot be hidden.
With PKCE, the client_secret
is never sent to the authorization server, preventing the client_secret
from being leaked from the client application.
Instead of using the client_secret
, you will need to generate a code_verifier
and code_challenge
and use them to exchange for an access token.
For example Dub Raycast extension uses PKCE to authenticate users.
Make an API request with the access token
Once you have obtained a valid access token, you can use it to make requests to the Dub API.
You can initialize Dub SDK with the access token.
Here is an example of how you can create a link using the Dub TypeScript SDK:
Or pass the access token in the header: Authorization: Bearer <ACCESS_TOKEN>
Refresh the access token
Dub access tokens are short-lived, depending on the expires_in
value. Dub will respond with 401 Unauthorized
if you try to use an expired access token.
To refresh the access token, you need to make a POST request to the Dub OAuth token URL with the refresh_token
you obtained when exchanging the code for an access_token
.
The Content-Type
header should be set to application/x-www-form-urlencoded
.
Parameters:
Property | Description |
---|---|
client_id | The client ID of your OAuth application. |
client_secret | The client secret of your OAuth application. |
grant_type | The grant type. It should be refresh_token . |
refresh_token | The refresh token you received when exchanging the code for an access token. |
Response:
After a successful request, you will receive a JSON response with the new access token.
This will invalidate the old access token and refresh token.
Scopes
You can request access to specific scopes when redirecting users to the Dub OAuth authorization URL. Scopes are permissions that the user needs to grant to your application.
Dub supports the following scopes for OAuth 2.0:
Scope | Description |
---|---|
workspaces.read | Read access to workspaces. |
workspaces.write | Write access to workspaces. |
links.read | Read access to links. |
links.write | Write access to links. |
tags.read | Read access to tags. |
tags.write | Write access to tags. |
analytics.read | Read access to analytics. |
domains.read | Read access to domains. |
domains.write | Write access to domains. |
user.read | Read access to user information. This scope is included by default. |
Examples
Integrating via API keys (not recommended)
Dub also supports API key authentication; however, it is not recommended for building integrations. It should only be used for internal integrations or personal projects that do not require user consent.
Learn more about API Keys.