> ## Documentation Index > Fetch the complete documentation index at: https://docs.stackone.com/llms.txt > Use this file to discover all available pages before exploring further. # Resend OAuth 2.0 connector profile – StackOne setup guide > Set up the OAuth 2.0 connector profile for Resend in StackOne. One-time admin setup required before your users can link Resend accounts via Hub.
Select Actions to adjust the guide
Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.
Action
Scope(s)
Loading actions...
Dynamic Guide URL
Scopes Selected

          

            
Separator

Register an OAuth client

Resend does not yet have a dashboard screen for creating OAuth clients, so you register one by calling the OAuth registration endpoint, as described in the Building a Resend OAuth client guide. Registration returns the Client ID and Client Secret you enter in StackOne.

Send a registration request to `POST https://api.resend.com/oauth/register`. Register a confidential client so that Resend issues a Client Secret, and include StackOne's callback URL as a redirect URI.

  • Set `client_name` to `StackOne Integration`.
  • Add StackOne's callback URL to `redirect_uris`: `https://api.stackone.com/connect/oauth2/resend/callback`
  • Include both `authorization_code` and `refresh_token` in `grant_types`. The `refresh_token` grant is required so StackOne can refresh the access token once it expires.
  • Set `token_endpoint_auth_method` to `client_secret_post`, because StackOne sends the client credentials in the request body when exchanging and refreshing tokens. Resend still issues a Client Secret for the confidential client.
  • The Client Secret is returned only once at registration and cannot be retrieved later — store it securely for use later.
Enables actions: Add Batch Suppressions, Add Suppression, Cancel Email, Create API Key, Create Broadcast, Create Contact, Create Domain, Create Segment, Delete API Key, Delete Broadcast, Delete Contact, Delete Domain, Delete Segment, List API Keys, List Broadcasts, List Contacts, List Domains, List Emails, List Segments, List Suppressions, Remove Batch Suppressions, Remove Suppression, Retrieve Broadcast, Retrieve Contact, Retrieve Domain, Retrieve Email, Retrieve Segment, Retrieve Suppression, Send Batch Emails, Send Broadcast, Send Email, Update API Key, Update Broadcast, Update Contact, Update Domain, Update Email, Update Segment, Verify Domain

Request the scopes this integration needs. Use full access for all API routes, or sending access to only send email.

Paste the returned `client_id` into the Client ID field and the `client_secret` into the Client Secret field in the StackOne Connector profile. In the Scopes field, enter the space-separated scopes you registered, such as `full_access`.
## Creating the StackOne Connector Profile To create the Connector Profile in StackOne for Resend: Login to StackOne and navigate to [Connector Profiles](https://app.stackone.com/connector_profiles)
  • Click + Connector Profile
  • Search for and select Resend
  • Select Type as OAuth 2.0
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
    • Scopes (Optional)
  • (Optional) Select Actions to be enabled for this Connector Profile
  • Click Create profile
 Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Resend. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.