Integrations

Ramp Webhooks Integration

Ramp webhooks provide real-time notifications for transactions, bills, applications, requests, users, vendors, and other supported business events.

Capture the original request first, enforce the available trust boundary, then route and replay from durable evidence.

How the integration works

  • Ramp returns a webhook secret when the subscription is created.
  • X-Ramp-Signature is a hexadecimal HMAC-SHA256 digest of the unmodified request body.
  • Ramp uses a verification event and API confirmation before activating a new endpoint.
  • Retryable failures can be attempted up to ten times with exponential backoff, and events may arrive out of order.

Create the FastHook source

Create RAMP source
curl -X POST "https://api.fasthook.io/v1/sources" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Ramp Webhooks Integration",
    "type": "RAMP",
    "config": {
      "auth_type": "PROVIDER_SIGNATURE",
      "auth": {
        "provider": "RAMP",
        "webhook_signing_secret": "ramp-webhook-secret"
      },
      "allowed_http_methods": ["POST"]
    }
  }'

Setup

  1. Create a RAMP source and copy its Source URL.
  2. Create a Ramp webhook subscription for the required event types and save its returned secret in FastHook.
  3. Inspect the webhooks.verification event and submit its challenge through Ramp's verification API.
  4. Send a test event, confirm signature verification, and route by type and business_id.

Production notes

  • Use event id as the idempotency key across retries.
  • Do not parse or reserialize the body before signature verification.
  • Fetch the current resource when event ordering could affect a financial workflow.

Related documentation