Prerequisites
The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Ramp connector page.Webhook subscription (managed by StackOne)
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.
Grant the right permissions to receive events
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 read scope — 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 every scope it is able to request, which covers all but the two partner-gated event types noted below. If you enter a smaller set of scopes in the optional Scopes field when connecting, events for the resources you left out will not be delivered.
- Also enable the same scopes on your Ramp developer app (under Scopes in the app settings) — Ramp will refuse the connection if it asks for a scope the app does not allow.
- Two events need no scope at all:
payments.updated(Ramp has no public scope for it) andtests.test_event(used only for delivery testing). - Two further events are gated on scopes Ramp does not offer to self-serve developer apps, so the connector cannot request them and they are not delivered on a standard connection:
applications.status_updated(needsapplications:read, issued only to third-party partner apps) andspend_requests.comment_created(needsspend_requests:read, enabled per integration under Ramp’s procurement intake partner flow). If Ramp has granted your app either scope, add it to the optional Scopes field when connecting.
Keep Webhook Endpoint Verification enabled
Ramp challenges the endpoint once before sending any events, and the Webhook Endpoint Verification action is what answers it. Leave this action enabled — if it is off, the subscription stays in pending_verification and no events are ever delivered, with no error shown.
- If it was already disabled, re-enable it and reconnect the account — Ramp only challenges a newly created subscription.