> ## 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.

# Better Stack OAuth 2.0 connector profile – StackOne setup guide

> Set up the OAuth 2.0 connector profile for Better Stack in StackOne. One-time admin setup required before your users can link Better Stack accounts via Hub.

Select Actions to adjust the guideSome actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.

Select all
Clear

ActionScope(s)

Loading actions...No actions match your search.

Dynamic Guide URL

Copy URL

Scopes Selected

<pre role="textbox" aria-readonly="true" tabIndex="0" />

Separator

Copy scopes

## Register an OAuth client

Better Stack has no dashboard screen for OAuth clients. Register one with a single request to its client registration endpoint.

**1. Register the client**

Enables actions: Acknowledge Incident, Create A Dashboard, Create A Dashboard Alert, Create A Dashboard Group, Create A Heartbeat, Create A Release, Create A Source, Create A Source Group, Create An Application, Create An On-call Schedule, Create An On-call Schedule Event, Create Catalog Attribute, Create Catalog Record, Create Catalog Relation, Create Comment, Create Escalation Policy, Create Heartbeat Group, Create Incident, Create Monitor, Create Monitor Group, Create Severity, Create Status Page, Create Status Page Report, Create Status Page Resource, Create Status Update, Escalate Incident, Get A Heartbeat's Availability Summary, Get A Single Alert, Get A Single Application, Get A Single Catalog Record, Get A Single Dashboard, Get A Single Dashboard Group, Get A Single Heartbeat, Get A Single On-call Schedule Event, Get A Single Release, Get A Single Source, Get A Single Source Group, Get An On-call Schedule Rotation, Get Catalog Attribute, Get Catalog Relation, Get Comment, Get Escalation Policy, Get Heartbeat Group, Get Incident, Get Monitor, Get Monitor Group, Get On-call Schedule, Get Severity, Get Severity Group, Get Status Page, Get Status Page Report, Get Status Page Resource, Get Status Update, List All Alerts, List All Applications, List All Dashboard Groups, List All Dashboards, List All Releases, List All Source Groups, List All Sources, List Catalog Attributes, List Catalog Records, List Catalog Relations, List Comments, List Escalation Policies, List Heartbeat Groups, List Heartbeats, List Incident Timeline, List Incidents, List Metadata, List Monitor Groups, List Monitors, List Monitors In Group, List On-call Schedule Events, List On-call Schedules, List Severities, List Severity Groups, List Status Page Reports, List Status Page Resources, List Status Page Sections, List Status Pages, List Status Updates Per Report, Monitor Availability, Monitor Response Times, Remove A Dashboard, Remove A Dashboard Group, Remove A Release, Remove A Source, Remove A Source Group, Remove An Alert, Remove An Application, Remove Catalog Attribute, Remove Catalog Record, Remove Catalog Relation, Remove Comment, Remove Escalation Policy, Remove Heartbeat, Remove Heartbeat Group, Remove Incident, Remove Monitor, Remove Monitor Group, Remove On-call Schedule, Remove On-call Schedule Event, Remove Severity, Remove Status Page, Remove Status Page Report, Remove Status Page Resource, Reopen Incident, Resolve Incident, Update A Dashboard, Update A Dashboard Group, Update A Source, Update A Source Group, Update An Alert, Update An Application, Update An On-call Schedule, Update Catalog Attribute, Update Catalog Record, Update Catalog Relation, Update Comment, Update Escalation Policy, Update Heartbeat, Update Heartbeat Group, Update Metadata, Update Monitor, Update Monitor Group, Update On-call Schedule Event, Update Severity, Update Status Page, Update Status Page Report, Update Status Page Resource

Run this request, replacing `<CALLBACK_URL>` with the **Callback URL** from your Connector Profile. Better Stack only supports public clients with PKCE, so no client secret is issued.

```bash theme={null}
curl -X POST 'https://betterstack.com/oauth/register' \
  -H 'Content-Type: application/json' \
  -d '{
    "client_name": "StackOne Integration",
    "redirect_uris": ["<CALLBACK_URL>"],
    "grant_types": ["authorization_code", "refresh_token"],
    "response_types": ["code"],
    "token_endpoint_auth_method": "none"
  }'
```

<ul>
  <li>`grant_types` must include `refresh_token` so StackOne can renew the access token.</li>
  <li>The client can request the `read` and `write` scopes.</li>
</ul>

<ul>
  <li>
    read
  </li>

  <li>
    write
  </li>
</ul>

**2. Copy the client ID**

Copy the `client_id` from the response into your Connector Profile as the **Client ID**.

## Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for **Better Stack**:

**1. Open the connector**

Log in to StackOne, open [Connectors](https://app.stackone.com/connectors), and select **Better Stack**.

**2. Choose actions and events**

<ul>
  <li>Click **Add Profile**.</li>
  <li>If the connector offers more than one authentication method, set the **Auth Method** filter to **OAuth 2.0**.</li>
  <li>Select the actions, and any events, to enable for this Connector Profile.</li>
  <li>Click **Continue**.</li>
</ul>

**3. Set up authentication**

<ul>
  <li>Select **Authentication Type** as **OAuth 2.0**.</li>

  <li>
    Fill out the fields using details retrieved from your provider:

    <ul>
      <li>**Client ID**</li>
      <li>**Scopes** (Optional)</li>
    </ul>
  </li>

  <li>Click **Create Profile**.</li>
</ul>

Congratulations! The new Connector Profile now shows up on the connector page. If you created it as a project member rather than an admin, it starts disabled until a project admin enables it. You can now continue to [Link Accounts](https://docs.stackone.com/connect/managing-connectors/linking-accounts.md) for **Better Stack**.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.