nowpayments.io APInowpayments.io ↗
Access NOWPayments via API: create payments and invoices, check payment status, get estimated prices, and query available cryptocurrencies across 8 endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/f1a5b5b1-1b18-4f85-ba15-f2ad2da90126/get_api_status' \ -H 'X-API-Key: $PARSE_API_KEY'
Check NOWPayments API availability and health. Returns a message indicating the API is operational. No API key required.
No input parameters required.
{
"type": "object",
"fields": {
"message": "string indicating API operational status"
},
"sample": {
"data": {
"message": "OK"
},
"status": "success"
}
}About the nowpayments.io API
The NOWPayments API provides 8 endpoints for integrating cryptocurrency payment processing into any application. Use create_payment to generate a crypto payment address and amount, create_invoice to produce a hosted payment link, or get_payment_status to poll a live payment's current state — including fields like pay_address, actually_paid, and payment_status. The API also covers currency discovery, minimum payment thresholds, and real-time conversion estimates.
Currency Discovery and Pricing
Two endpoints cover available currencies. get_available_currencies returns a flat array of currency code strings and accepts an optional fixed_rate filter (requires an API key). get_full_currencies returns richer objects that include per-currency limits and logos. Before creating a payment, get_minimum_payment_amount accepts a currency_from/currency_to pair and returns the min_amount for that route, with optional is_fixed_rate and is_fee_paid_by_user flags. get_estimated_price takes an amount, source currency, and destination currency, and returns estimated_amount alongside the echoed currency_from and currency_to — useful for showing users what they'll actually pay.
Creating Payments and Invoices
create_payment accepts a required price_amount and price_currency (e.g., usd) plus optional pay_currency, order_id, order_description, and customer_email. It returns a payment_id, pay_address, pay_amount, and initial payment_status. create_invoice follows the same input shape but returns an invoice_url instead of a direct address — suited for redirect-based checkout flows where you don't want to handle address display yourself.
Payment Status and Health
get_payment_status accepts a payment_id and returns payment_status, pay_address, price_amount, and actually_paid — the last field being the amount the customer has sent so far, which matters for partial-payment detection. The get_api_status endpoint requires no API key and returns a single message field confirming whether the NOWPayments service is reachable; useful as a pre-flight check in uptime monitors or CI pipelines.
- Display real-time crypto conversion estimates to customers before checkout using
get_estimated_price - Generate hosted invoice URLs for e-commerce order fulfillment with
create_invoice - Poll
get_payment_statusto confirm when a payment reaches a completed or partially-paid state - Enforce minimum deposit thresholds in a crypto exchange UI using
get_minimum_payment_amount - Build a currency selector dropdown populated with logos and limits from
get_full_currencies - Run an uptime monitor or health check dashboard against
get_api_statuswithout consuming API credits - Filter available fixed-rate currencies for a fixed-price storefront using the
fixed_rateparameter onget_available_currencies
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does NOWPayments have an official developer API?+
What does `get_payment_status` return, and can it detect partial payments?+
get_payment_status returns payment_id, pay_address, price_amount, payment_status, and actually_paid. The actually_paid field reflects the amount received so far, so you can compare it against price_amount to identify underpayments before the payment reaches a terminal status.What is the difference between `create_payment` and `create_invoice`?+
create_payment returns a raw pay_address and pay_amount that your application must render. create_invoice returns an invoice_url pointing to a NOWPayments-hosted checkout page, so you can redirect customers without building your own payment UI.Does the API expose payment history or a list of past transactions?+
payment_id, plus currency and pricing utilities. There is no endpoint for listing historical payments or filtering by date range. You can fork this API on Parse and revise it to add an endpoint that fetches payment history if NOWPayments exposes that route on your account.