Authentication

All API requests require authentication using an API key.

API Key

Include your API key as a Bearer token in the Authorization header:

Authorization: Bearer YOUR_API_KEY

API keys are project-scoped. Each key grants access to resources within a single project.

API Versioning

Include the Reap-Version header in every request to specify which API version to use:

Reap-Version: 2025-02-14

The version uses a date-based format (YYYY-MM-DD). Requests without this header will be rejected.

Example

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

Environments

Environment	Base URL
Singapore sandbox	`https://sg.sandbox.api.reap.global`
Singapore production	`https://sg.prod.api.reap.global`
Mexico sandbox	`https://mx.sandbox.api.reap.global`
Mexico production	`https://mx.prod.api.reap.global`

https://sandbox.api.reap.global and https://prod.api.reap.global remain valid aliases for Singapore. API keys are scoped to a single environment. A sandbox key cannot be used against production and vice versa.

Contact the Reap team to obtain API keys for your project.

Setup

Users

Companies

Accounts

Virtual Asset Postings

Cards

Card Shipments

Card Designs

Crypto Deposits

Crypto Withdrawals

Fiat Deposits

Card Transactions

Fraud Alerts

Disputes

Activities

Policies

Simulation

Virtual Assets

Webhooks

Agentic

API Key

API Versioning

Example

Environments

​API Key

​API Versioning

​Example

​Environments

API Key

API Versioning

Example

Environments