Overview

Build on Ramp

Ramp is the finance platform that 70,000+ businesses run their spend on. The Developer API opens that platform to your code: issue cards against enforced budgets, create and pay bills, sync a customer's ERP two ways, and give AI agents payment authority that respects your policy.

Every endpoint runs on the same policy engine as the Ramp dashboard. A fund's limit holds whether the spend comes from a person, a card, or an agent.

What you can build#

Ramp's API surface covers 170 endpoints across nine product areas. These are the journeys developers start with.

Goal Where to start Typical time
Read transaction data into a warehouse or dashboard Quickstart 5 minutes
Issue virtual cards inside your own product Cards and Funds 1–3 hours
Pay vendors end to end without leaving your stack Bill Pay Half a day
Sync a customer's chart of accounts and export spend Procurement Multi-day
Let an AI agent make a real purchase under policy Agent Cards 30–60 minutes

How Ramp fits together#

Four objects explain most of the API. Funds hold the budget and its restrictions. Cards draw against funds. Users are the principal behind every spend object. Approvals decide what passes before money moves.

Everything else — bills, reimbursements, purchase orders, agent purchases — composes those four. Learn them once in Spend Controls and the rest of the surface reads as variations.

Free to start
Make your first API call

Create a developer app in the Ramp dashboard, mint a token, and pull real transactions.