Get Started
Base URL
The Base URL for accessing Prune's API services is:
https://dps.prunepayments.net
Our API services are primarily divided into two main categories:
Account Service: This service enables you to manage both individual and organizational accounts.
Payout Service: This service provides access to payment functionalities, such as requesting payouts and transferring funds between accounts.
API Status Codes
The API Status Codes section outlines the standard HTTP status codes that the Prune API may return in response to your requests. These codes are crucial indicators of the outcome of an API request. Common examples include:
200 OK: Indicates that the request was successful.401 Unauthorized: Signifies an authentication failure, meaning the request lacks valid authentication credentials.500 Internal Server Error: Points to a server-side issue that prevented the API from fulfilling the request.
Below is a comprehensive list of all statuses that may be returned when using the Prune API Service:
(Note: The comprehensive list of status codes would typically follow here in the actual documentation.)
🟢
200
OK
The request was successful and the server returned the requested data.
🟢
201
Created
The request was successful and a new resource was created.
🟢
202
Accepted
The request has been accepted for processing, but the processing has not been completed.
🔴
400
Bad Request
The server could not understand the request due to invalid syntax.
🔴
401
Unauthorized
Authentication is required and has failed or has not yet been provided.
🔴
403
Forbidden
The client does not have access rights to the content.
🔴
404
Not Found
The server cannot find the requested resource.
🔴
500
Internal Server Error
The server encountered an internal error and was unable to complete the request.
🟡
503
Service Unavailable
The server is not ready to handle the request, usually due to maintenance or overload.
Postman Collection
The Postman Collection offers a set of pre-configured API requests for the Prune API. This allows you to quickly and easily test and interact with its various routes and endpoints.
Last updated