Request Parameters

For a Prune API request to be successful, specific parameters must be included. These parameters may vary depending on the endpoint being accessed but generally include:

• Bearer Token: The authentication token generated from your service dashboard, essential for authenticating your request.

• Endpoint-Specific Parameters: Each endpoint may require additional parameters, such as a user ID, account details, query strings, or other relevant data specific to the operation you are performing.

Example of a cURL Request

Here's how you can make a GET request to one of the Prune API endpoints using a cURL command:

# Example cURL command (replace with actual endpoint and token)
curl -X GET \
  'https://api.prune.com/v1/accounts/endpoint>' \
  -H 'Authorization: Bearer YOUR_AUTHENTICATION_TOKEN' \

In this example:

• X GET specifies the type of HTTP request.

• https://dps.prunepayments.net is the base URL.

• "<https://dps.prunepayments.net/endpoint>" is the endpoint URL.

• "<https://dps.prunepayments.net/ v1/accounts/request-corporate-account" example for account request.

• H "Authorization: Bearer YOUR_TOKEN" includes the authorization header with the Bearer Token.