Skip to main content
The Ripio Wallet API allows third-party integrations to access wallet data on behalf of users. All requests must be authenticated with the key / secret pair issued by Ripio, and must have the required permissions for each endpoint. All requests and responses use JSON format (application/json). More endpoints will be made available with time.

Success

All successful requests return an HTTP 2xx status with the following body:
On success, error_code and message are always null. The response payload is in data.

Error

On error, error_code and message are populated. data is null for simple errors, or contains field-level details when there are multiple validation errors. Single error:
Multiple field errors (e.g. form validation):
When data is present on an error, it maps each field name to its list of errors — useful for highlighting specific form inputs on the client side. Authentication / authorization error:

Generic error codes

Upstream-specific codes (e.g. TXN_0420, NET_0001) are passed through as-is. Generic ERR_XXXX codes are only used as fallback when no upstream code is present.