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

# Ramp Webhook Setup Guide

> Configure Ramp to deliver events to StackOne.

## Prerequisites

Before continuing, you should have already completed the following for this connector:

<Steps>
  <Step title="Configure the Connector">
    Enable the connector and set up its connector profile in your project. See <a href="/guides/explore-connectors">Managing Connectors</a>.

    <Columns cols={2}>
      <Card title="Connector Profile" href="/connectors/ramp/guides/connector-profile/oauth-2-0" icon="https://stackone-logos.com/api/ramp/filled/png" horizontal>
        Ramp - OAuth 2.0
      </Card>
    </Columns>
  </Step>

  <Step title="Link an Account">
    Connect an account using <a href="/guides/embedding-stackone-hub">StackOne Hub</a> or <a href="/guides/auth-link">Auth Link</a>.

    <Columns cols={2}>
      <Card title="Link Account" href="/connectors/ramp/guides/link-account/oauth-2-0" icon="https://stackone-logos.com/api/ramp/filled/png" horizontal>
        Ramp - OAuth 2.0
      </Card>
    </Columns>
  </Step>
</Steps>

<section data-guide-section data-guide-scopes="">
  <h2>Webhook subscription (managed by StackOne)</h2>

  <p>You do not need to set up anything in the Ramp dashboard to receive webhook events. When you connect your Ramp account, StackOne automatically registers a webhook subscription with Ramp, completes Ramp's verification handshake, and starts receiving events. When you disconnect the account, StackOne removes the subscription again — the entire lifecycle is handled for you.</p>

  <Steps>
    <Step title="Grant the right permissions to receive events">
      <div data-guide-step data-guide-scopes="" data-guide-display-scopes-list="">
        <p>Ramp only sends events for the resources your connection is allowed to read. To receive a resource's events, your connection needs that resource's <strong>read scope</strong> — for example, transaction events require `transactions:read`, bill events require `bills:read`, and unified request events require `unified_requests:read`. By default the connector requests all of its scopes, so every event type is covered. If you enter a smaller set of scopes in the optional <strong>Scopes</strong> field when connecting, events for the resources you left out will not be delivered.</p>

        <ul>
          <li>Also enable the same scopes on your <strong>Ramp developer app</strong> (under Scopes in the app settings) — Ramp will refuse the connection if it asks for a scope the app does not allow.</li>
          <li>Two exceptions need no scope at all: `payments.updated` (Ramp has no public scope for it) and `tests.test_event` (used only for delivery testing).</li>
        </ul>
      </div>
    </Step>
  </Steps>
</section>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.