Overview

REST API with JSON request and response bodies.

Base URLs

Environment	Base URL
Sandbox	`https://sandbox.api.reap.global`
Production	`https://prod.api.reap.global`

Sandbox and production are fully isolated. API keys, webhooks, and data live in one environment and never cross.

Every request must include:

Header	Description
`Authorization`	Your API key as a Bearer token: `Bearer YOUR_API_KEY`
`Reap-Version`	API version in YYYY-MM-DD format. Current version: `2025-02-14`
`Content-Type`	`application/json` for requests with a body

curl https://sandbox.api.reap.global/users \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Reap-Version: 2025-02-14"

Monetary and rate fields use different JSON types depending on what they represent, chosen so partners never silently lose precision:

Field shape	JSON type	Notes
Fiat amounts (USD, EUR, …)	`number`	At the currency’s native precision (2 decimal places for most fiat). Safe to read as a JS `number`.
Crypto and virtual asset amounts	`string`	Decimal string padded to the asset’s `decimals` (e.g. `"1.000000"` for 1 USDC). Lossless across all values; compare and arithmetic via a big-decimal library.
Exchange and conversion rates	`number`	6 decimal places.

A field’s individual description always wins when it differs. The same conventions are followed on input bodies.

⌘I