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

# Connect Rillet with API Key – StackOne Hub

> Link a Rillet account in the StackOne Hub using API Key. End-user guide to authorize the integration and start using Rillet actions.

<Warning>API access is not enabled by default. Contact your Rillet team to turn it on for your organization before you try to create a key, otherwise the API Access page will be empty.</Warning>

<section data-guide-section data-guide-scopes="">
  <h2>Create a Rillet API key</h2>

  <p>Rillet authenticates every request with a bearer API key issued per organization. Create one in Organization Settings, then paste it into StackOne Hub along with the environment you want to connect.</p>

  <Steps>
    <Step title="Ask Rillet to enable API access">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>API access is gated per organization. Contact your Rillet team and ask them to enable API access for your account. Until they do, the API Access settings page will not let you create keys.</p>
      </div>
    </Step>

    <Step title="Open Organization Settings > API Access">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Sign in to <a href="https://app.rillet.io" target="_blank" rel="noopener noreferrer">Rillet</a> as a user whose role permits managing API keys, then go to <a href="https://app.rillet.io/settings/api-access" target="_blank" rel="noopener noreferrer">Organization Settings > API Access</a>.</p>
      </div>
    </Step>

    <Step title="Create the key and copy it">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Create a new API key and copy the value straight away — it is shown only once.</p>

        <ul>
          <li>Keys do not expire. Revoking a key in Rillet takes effect immediately and will break any StackOne connection still using it.</li>
          <li>The key acts with the Rillet role permissions of the user who created it. If some actions return 403 Forbidden while others succeed, the key is valid but that user's role does not permit the operation.</li>
        </ul>
      </div>
    </Step>

    <Step title="Choose the matching environment">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>When you create the connection in StackOne, select <strong>Production</strong> to reach your live Rillet organization or <strong>Sandbox</strong> to reach the Rillet test environment. Rillet runs the two as separate systems with separate keys, so the environment you pick must match where the key was created — a production key will not authenticate against the sandbox, and vice versa.</p>
      </div>
    </Step>

    <Step title="Paste the key into StackOne">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Paste the key into the <strong>API Key</strong> field in StackOne Hub and save the connection. StackOne verifies it by calling the Rillet API key information endpoint, which confirms both that the key is recognised and which organization it belongs to.</p>
      </div>
    </Step>
  </Steps>
</section>

<div data-whitelabel-hide>
  <h2>Linking the Account from the Hub</h2>

  <Steps>
    <Step title="Navigate to the Hub">
      Use one of the three <a href="/connect/managing-connectors/linking-accounts">Linking Account Methods</a> to access the Hub.
    </Step>

    <Step title="Fill out the fields">
      Fill out the following fields using details from your provider:

      <ul>
        <li><strong>API Key</strong></li>
      </ul>
    </Step>

    <Step title="Connect">
      <ul>
        <li>Click <strong>Connect</strong></li>
        <li>If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider's authorization flow.</li>
        <li>Once authorization is successful, you will see a confirmation popup</li>
      </ul>
    </Step>
  </Steps>

  <p>If the account linking is successful, you will see the newly linked account in your <a href="/gateway/concepts/linked-accounts">Accounts</a> page.</p>
</div>