Ramp

Ramp’s Developer API lets us pull card transactions, reimbursements, vendors, and spend programs to power reporting on spend by team and location, vendor concentration, and cost per employee. You’ll create an app in your own Ramp account using the Client Credentials OAuth flow — a server-to-server grant with no browser redirect — and then paste its Client ID and Client Secret into our connection form. You’ll need admin access to your Ramp account to reach the Developer settings.

The scopes you select define exactly what we can read. Ramp issues our access token with every scope your app is registered for, so the app you create in step 1 is the real boundary on our access — not anything configured on our side. Grant only the read scopes in step 2, and in particular leave cards:read_vault unchecked: it exposes raw card numbers and CVVs, we never request it, and we have no use for it.

Create an app in Ramp

In the Ramp web app, go to Company → Developer and click Create New App.
Name: Human Intelligence Data Sync, then accept the Terms.
Under Grant types, click Add new grant type and choose Client Credentials. Don’t add Authorization Code — we don’t use it for this connection.

Configure the allowed scopes

Still in your app, click Configure allowed scopes under Scopes and select the 28 read scopes below. Every one is read-only — no :write scope is needed. Skip any row for a Ramp product your plan doesn’t include; we’ll simply have no data for it.

Scope	Why we need it
`accounting:read`	Your GL accounts, tracking categories, tax rates, and accounting sync status — how Ramp spend maps to your books.
`audit_logs:read`	Audit log events — who approved or changed what, for approval and control reporting.
`bank_accounts:read`	Linked bank account metadata, to label the funding source of transfers.
`bills:read`	Bills and bill drafts — accounts-payable volume and aging.
`business:read`	Your business profile and overall balance — the top-level totals every report rolls up to.
`cards:read`	Physical and virtual card metadata (limits, status, owner) — not card numbers.
`cashbacks:read`	Cashback earned, which offsets reported net spend.
`custom_records:read`	Custom, native, and matrix tables, so any spend dimensions unique to your org come through.
`departments:read`	Department names, for spend by team.
`entities:read`	Legal entities, so multi-entity businesses can be reported separately.
`funds:read`	Fund balances backing spend programs.
`item_receipts:read`	Line-item receipt detail, for category-level breakdowns.
`locations:read`	Location names, for spend by site or region.
`memos:read`	Transaction memos, which carry coding and justification notes.
`merchants:read`	Merchant names and categories, for vendor concentration and category mix.
`purchase_orders:read`	Purchase orders, to match committed spend against actuals.
`receipts:read`	Receipt metadata attached to transactions, for compliance and match rates.
`reimbursements:read`	Employee out-of-pocket expense reimbursements.
`repayments:read`	Card balance repayments, for cash-flow reporting.
`spend_programs:read`	Spend programs and their approval workflow steps — how budgets are structured.
`statements:read`	Billing statements, for period-over-period reconciliation.
`transactions:read`	Card transactions — the core spend record behind every spend metric.
`transfers:read`	Transfers between Ramp and your bank accounts.
`treasury:read`	Ramp Business Account balances and history, if you use Ramp Treasury.
`trips:read`	Travel bookings, if you use Ramp Travel.
`unified_requests:read`	Spend and card requests, for approval-cycle time.
`users:read`	Employees on the account, so spend can be attributed per person and per manager.
`vendors:read`	Vendor records, contacts, and linked accounts for accounts-payable analysis.

Do not select: cards:read_vault (raw card numbers and CVVs) or any :write scope. We never call a write endpoint, and our integration refuses to request the vault scope outright.

Enter your credentials

Ramp shows the Client Secret once, when the app is created — copy it before leaving the page. If you lose it, you can generate a new secret from the same app.

Click Connect above to open the connection form.
Enter your app’s Client ID.
Enter your app’s Client Secret.
Click Connect to save.

Security and API details

Setting	Detail
Authentication	OAuth 2.0, client credentials grant
Token endpoint	https://api.ramp.com/developer/v1/token
API base URL	https://api.ramp.com
Access	Read-only — no :write scopes are ever requested
Card data	Metadata only. cards:read_vault (raw PAN/CVV) is never requested.
Credential storage	Encrypted at rest and scoped to your organization; all traffic runs over TLS.
Revoking access	Delete the app under Company → Developer in Ramp, or disconnect from Integrations → Ramp here.

Questions? Contact us at support@humanintelligence.com.

Get Started

Connectors

MCP

Data

Metrics & Definitions

Governance

Security

Create an app in Ramp

Configure the allowed scopes

Enter your credentials

Security and API details

​Create an app in Ramp

​Configure the allowed scopes

​Enter your credentials

​Security and API details

Create an app in Ramp

Configure the allowed scopes

Enter your credentials

Security and API details