General

The ANONPAY API enables users to process payments privately.
It accepts GET and POST requests, allowing data to be sent through both types of parameters.
We do not log any API requests.

Our API is currently hosted on the following mirrors:



Our Checkout is currently hosted on the following mirrors:


We recommend using the onion-based endpoints for lower latency and to ensure authenticity of API calls.
Note that a TOR SOCKS5 proxy is required to query these endpoints.

Authentication

Authentication is based on the "key" parameter, which must contain your API key and can be included in either POST form data or GET parameters.
If you do not have an API key, you can obtain one here.

Query Params / Form Data

key string required
abcdefghijklmnopqrstuvwxyz0123

Contains your API key.
Get it from here.

Error Handling

All endpoints return a status field that contains either “success” or “error”.
Here is a possible error response:

Response JSON

status string required

Contains the status of the API request.

error string required on error
parameter_missing

Contains an error string depending on your error.
Possible errors include: “parameter_missing”, “parameter_invalid”

code string required on error
abc123

Contains a code used for debugging purposes.

Webhook

Webhooks allow you to get live updates about active transactions.
If a webhook is configured, a GET request will be sent to your specified URL from a TOR exit node, so make sure to allow TOR traffic on your selected endpoint.
Make sure to validate the received "private_key" to prevent spoofed requests!
The request can contain the following GET parameters:

Query Params

transaction_id string required
abcdefghijklmnopqrstuvwxyz0123

Contains the transaction ID about which information is sent.

private_key string required
abcdefghijklmnopqrstuvwxyz0123

Contains a transaction's private key.
It can be used to verify webhook requests are valid.

event string required

Contains the event that triggered the webhook request.