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

# Getting Started

> The path to embedding StackOne in your product, from setup to production.

Bring StackOne into your own product: connect your users' accounts and call connector actions from your code. Here's the path end to end.

<Note>
  Just exploring, or prefer a no-code route? Start with the [Quickstart](/gateway/quickstart) to connect your first connector from the dashboard.
</Note>

<Steps>
  <Step title="Set up your project and API key">
    <Card title="API Keys" icon="key" href="/embed/api-keys">
      Create a project and an API key with the scopes **Actions** and **Platform API**.
    </Card>

    This **API key** will be used to authenticate all backend and API calls below.
  </Step>

  <Step title="Enable a connector for your users to link accounts with">
    <Card title="Connector Profiles" icon="plug" href="/gateway/quickstart#setup-connector-profile">
      A Connector Profile configures a provider's authentication and the actions your users can use.
    </Card>

    This sets up a [**connector profile**](/gateway/concepts/connector-profiles) for the provider you chose (e.g. `hubspot`) — its authentication and enabled actions — which you target when creating a session.
  </Step>

  <Step title="Generate a connect session">
    <Card title="Connect Session" icon="server" href="/embed/connect-session">
      Instantiate a connect session on your backend to open the linking flow for a specific user.
    </Card>

    Using your **API key** and **provider** from the previous steps, this returns a short-lived **session token** for the frontend.
  </Step>

  <Step title="Implement and display the Hub for your users to link accounts">
    <CardGroup cols={2}>
      <Card title="Hub Account Linking" icon="window" href="/embed/account-linking/overview">
        Open the Hub or send an Auth Link so users connect their accounts.
      </Card>

      <Card title="Handle Account Events" icon="webhook" href="/embed/handle-account-events">
        React to accounts being linked, updated, or disconnected.
      </Card>
    </CardGroup>

    The Hub is initiated using the **session token**. Once a user links an account, the Hub returns its **account ID** (or you pick it up from the **account event**) for calling actions.
  </Step>

  <Step title="Call actions from your code">
    <Card title="Call Actions" icon="code" href="/embed/call-actions/overview">
      Use the protocol that fits your stack — the Agent SDK, MCP, A2A, or RPC/HTTP.
    </Card>

    Every call uses your **API key** and the **account ID** from the previous step, selecting which [linked account](/gateway/concepts/linked-accounts) to act on.
  </Step>
</Steps>

## Before you go to production

<CardGroup cols={2}>
  <Card title="OAuth Apps" icon="id-badge" href="/connect/managing-connectors/using-your-own-oauth-apps">
    Your brand on the consent screen and dedicated rate limits.
  </Card>

  <Card title="Webhooks" icon="bell" href="/connect/webhooks">
    React to account and data changes.
  </Card>

  <Card title="Request Logs" icon="chart-line" href="/connect/troubleshooting">
    Inspect calls, debug failures, and watch rate limits.
  </Card>
</CardGroup>