Skip to main content
The Reap Business Account API connects your Business Account to your own systems. What your finance and operations teams do by hand in the dashboard (deciding who can spend, setting budgets and limits, keeping track of spend and balances, and funding the account), your own software can do automatically, at the moment it’s needed.

Quickstart

From a new API key to your first card in a few calls.

Use cases

End-to-end flows for team cards, advertising campaigns and Treasury funding.

Concepts

Cards, spend controls, approvals, balances and Treasury explained.

API reference

Every endpoint, field and error code, plus the Changelog.

​
What the API does

The Business Account API lets you build your company’s spend management into the tools you already use: your HR system, your ERP or your internal admin tools. Instead of someone logging in to the dashboard, your systems act on your Business Account directly (issuing cards, setting limits, moving funds in) with the same controls and security as the dashboard.
  • See who on your team can hold a card
  • Create, rename, freeze and close virtual cards
  • Set budgets, spending limits and allowed hours per card
  • Show a card number, expiry and CVV in a secure, Reap-hosted window
  • Check spend per card, account activity and available credit
  • Get the funding information for your card account by bank transfer or crypto
  • Reconcile every movement on your balances

​
What it is not

Knowing the boundaries early saves time when you scope a project:
  • It’s for your own business. The API acts on your company’s Business Account, for your own team. It isn’t a platform for building financial products for your own customers or end users.
  • It doesn’t move funds out. Treasury endpoints give you the funding information for your own balances; paying third parties isn’t part of the Business Account API.
  • Control stays with your administrators. API keys are created and revoked by team administrators in the Business Account dashboard. A key can never create or manage other keys.
  • It works alongside the Business Account web app, not instead of it. The API automates parts of your Business Account, but some functionality is only available in the dashboard. Your team will keep using the web app alongside your integration.

​
What stays in the dashboard

​
Use cases you can unlock

Connect your HR system so every new joiner automatically gets a virtual card with limits that match their role, and their cards are closed on their last day. See Issue cards to your team. For the dashboard side of offboarding, see Handling a Departing Employee’s Reap Card in the Help Center.
Give every ad account or campaign its own card with a fixed budget. Spend is attributed automatically, one campaign can’t eat another’s budget, and a blocked card affects only one campaign. See Cards for advertising at scale.
Get the funding information for your card account by bank transfer or crypto from your own systems, confirm transfers automatically, and reconcile every movement against your accounting system. See Retrieve funding instructions and Treasury history.
Create a dedicated card for each software subscription or supplier. When you cancel a vendor, close its card, and unwanted renewals are declined automatically.
Create a card with a set budget for a business trip, event or project from your booking or project tool, then close it when the trip or project ends.
Pull spend and account balances into your BI tool, ERP or internal dashboard. Set alerts when a budget is nearly used up, or freeze cards automatically when your own rules are broken.

​
Know before you build

  • No sandbox Coming soon: every request is production. Test with low spend caps.
  • No webhooks Coming soon: poll list endpoints for changes.
  • No MCP server Coming soon: the Business Account API will be usable from Claude Code, Codex or any tool that can connect to a remote MCP server over HTTP, using the same API key and scopes.
  • Expenses Coming soon: uploading receipt notes and updating categories are coming soon.
  • Virtual cards only: the API can’t order physical cards.
  • Fiat funding is Card-only.
  • Expecting to create a significant number of cards? Reach out to our team first.

​
For agents and automated jobs

  • Every call is production. Create test cards with a spendCap of a few dollars and terminate them when done.
  • Never run card creation in a loop without an Idempotency-Key.
  • Use GET /health for connectivity checks, never a write.
  • Send creates one after another, not in parallel bursts.
  • See Polling and waiting for every poll cadence and stop condition.

​
Base URL

All endpoints are served over HTTPS only and versioned by date in the URL, for example https://api.global.direct.reap.global/2026-07-13/cards.

​
Getting access

The Business Account API is in Beta: the 2026-07-13 version is stable in production while the docs and coverage keep growing. Access is granted per business. See Access and API keys for how to request it, create a key and choose scopes, including the Treasury scopes and their eligibility rules.

​
Getting help

If something isn’t working, contact your Reap account manager or Reap support. Include the requestId from the error response; it lets the team find your exact request. See Know who to talk to @ Reap in the Help Center.