API reference
Eight endpoints. One page each, so you can link a colleague to the exact one rather than to a heading two thirds of the way down something longer.
| Method | Path | Does |
|---|---|---|
POST | /v1/partners/payments | Create a payment — give a customer something to pay with |
GET | /v1/partners/payments | List payments — the reconciliation endpoint |
GET | /v1/partners/payments/{id} | One payment, current status |
POST | /v1/partners/quotes | What a payment would cost, without creating one |
GET | /v1/partners/balance | What you can pay out right now |
POST | /v1/partners/payouts | Move your balance to a bank account |
GET | /v1/partners/payouts | List payouts |
GET | /v1/partners/payouts/{id} | One payout, current status |
What every endpoint shares
Section titled “What every endpoint shares”| Property | Value |
|---|---|
| Base URL | https://api-stg.moriafund.com/v1/partners (staging) · https://api.moriafund.com/v1/partners (production) — see Environments |
| Auth | Authorization: Bearer <api_key> and x-partner-signature — both, every call |
| Content-Type | application/json |
| Success | { "data": …, "request_id": "…" } |
| Failure | { "error": { "code", "message" }, "request_id": "…" } — see Errors |
The two money-moving endpoints — create a payment, request a payout — additionally require X-Idempotency-Key. That header is the difference between a safe retry and a second charge, and it has its own page.
Amounts are strings in both directions. You send "100000"; we answer "100000.0000". A JSON number is an IEEE-754 double and money must not pass through one.