Skip to main content
The API Reference in this section documents Reeple’s server-side REST API, hosted at:
This is a separate surface from the checkout SDK documented elsewhere in these docs. The SDK uses a publicKey (pk_live_.../pk_test_...) from the browser to open a checkout modal. This API uses a secret key (sk_live_.../sk_test_...) from your server to manage bank accounts, bill payments, payouts, transactions, and most other operations covered in this section.
S2S Payments is the one exception: those endpoints authenticate with your dashboard public key (pk_live_.../pk_test_...) in a public-key header, not the secret-key api-key scheme described below. See the S2S Payments overview for details.

​
Obtaining your keys

Reeple doesn’t currently offer self-service key generation. To get your public and secret keys, contact Reeple as part of onboarding.
Keys are issued in matching pairs per environment — a sk_test_... secret key is only valid alongside a pk_test_... public key, and likewise for sk_live_... / pk_live_.... Don’t mix a test key with a live one.

​
Authenticating a request

Send your secret key in the api-key header on every request:
Your secret key grants full access to your account’s financial data and operations. Keep it server-side only — never expose it in client-side code, mobile apps, or public repositories. Always call this API over HTTPS.
If you suspect a secret key has been compromised, contact Reeple immediately to have it rotated. Once a key is rotated, the old one stops working right away, so update your servers before requesting a rotation.

​
Next steps

Webhooks

Get notified in real time as your transactions change status.

Errors

Common error shapes returned across this API.