Base URLs
OpenAPI listsservers for tooling and the interactive playground. Paths in this spec already include the /v1 prefix (for example POST /v1/request-money), so the server URL is the host base only—do not append /v1 to the OpenAPI server value.
| Environment | Host base URL (BASE_URL in samples) | Versioned API root |
|---|---|---|
| Sandbox (Banrural) | https://banrural-request-api-sandbox.up.railway.app | https://banrural-request-api-sandbox.up.railway.app/v1 |
| Production | Provided by your integration contact | {production-host}/v1 |
https://banrural-request-api-sandbox.up.railway.app/v1/request-money.
You can regenerate the exported spec from the API repo with OPENAPI_SERVER_URL set so servers reflects another deployment.
Common headers
| Header | Required | Purpose |
|---|---|---|
Content-Type: application/json | On POST | Request body is JSON. |
X-API-Key | On POST and GET under /v1/request-money | Integrator authentication. |
Response format
- Success responses return JSON bodies defined in OpenAPI (
RequestMoneyResponse, status payloads, etc.). - Error responses use the shapes in OpenAPI for each status code. For example,
404onGET /v1/request-money/{referenceId}returnserror(stable machine-readable code such asnot_found) andmessage(human-readable text you can surface in support tooling or UX).401and422use their own DTOs (message, and for422adetailsobject).
HTTP status codes (surface summary)
| Code | Typical use |
|---|---|
| 201 Created | Successful POST /v1/request-money. |
| 200 OK | Successful GET /v1/request-money/{referenceId}. |
| 401 Unauthorized | Invalid or missing API key. |
| 403 Forbidden | POST blocked by screening (for example OFAC). |
| 404 Not Found | Unknown referenceId for GET. |
| 422 Unprocessable Entity | Validation or semantic errors on create. |
Rate limits and pagination
This specification does not define global rate limits or cursor pagination for the current two-endpoint surface. If your deployment adds limits, your integration contact will document them.Where to go next
Use the Endpoints group in the API Reference tab forcreateRequest and getByReferenceId, including schemas, examples, and the interactive playground.