NOWPayments

Cryptocurrency payment gateway for iGaming with invoices, payouts, and multi-coin support.

Detail	Value
Category	iGaming
Base URL	https://api.nowpayments.io/v1
Authentication	API Key
Endpoints	11
Connector key	nowpayments

Using NOWPayments in a workflow

1. Go to Connections and click New Connection.
2. Pick NOWPayments from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /status	API availability
GET /currencies	Available cryptocurrencies
GET /merchant/coins	Merchant-activated currencies
GET /estimate	Exchange price estimate
GET /min-amount	Minimum payment amount
POST /payment	Create crypto payment
GET /payment/{payment_id}	Payment status
GET /payment/	List payments
POST /invoice	Create invoice with QR
POST /payout	Mass payout
GET /balance	Account balance

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /status

API availability

Detail	Value
Operation ID	igaming.getStatus
Method	GET
Path	/status

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getStatus.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

GET /currencies

Available cryptocurrencies

Detail	Value
Operation ID	igaming.getCurrencies
Method	GET
Path	/currencies

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getCurrencies.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

GET /merchant/coins

Merchant-activated currencies

Detail	Value
Operation ID	igaming.getMerchantCoins
Method	GET
Path	/merchant/coins

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getMerchantCoins.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

GET /estimate

Exchange price estimate

Detail	Value
Operation ID	igaming.getEstimate
Method	GET
Path	/estimate

Parameters

Name	Location	Type	Required
amount	query	number	No
currency_from	query	string	No
currency_to	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getEstimate.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

GET /min-amount

Minimum payment amount

Detail	Value
Operation ID	igaming.getMinAmount
Method	GET
Path	/min-amount

Parameters

Name	Location	Type	Required
currency_from	query	string	No
currency_to	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getMinAmount.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

POST /payment

Create crypto payment

Detail	Value
Operation ID	igaming.createPayment
Method	POST
Path	/payment

Parameters

No parameters.

Request Body

Field	Type
price_amount	number
price_currency	string
pay_currency	string
order_id	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.createPayment.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

GET /payment/{payment_id}

Payment status

Detail	Value
Operation ID	igaming.getPayment
Method	GET
Path	/payment/{payment_id}

Parameters

Name	Location	Type	Required
payment_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getPayment.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

GET /payment/

List payments

Detail	Value
Operation ID	igaming.listPayments
Method	GET
Path	/payment/

Parameters

Name	Location	Type	Required
limit	query	integer	No
page	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.listPayments.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

POST /invoice

Create invoice with QR

Detail	Value
Operation ID	igaming.createInvoice
Method	POST
Path	/invoice

Parameters

No parameters.

Request Body

Field	Type
price_amount	number
price_currency	string
order_id	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.createInvoice.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

POST /payout

Mass payout

Detail	Value
Operation ID	igaming.createPayout
Method	POST
Path	/payout

Parameters

No parameters.

Request Body

Field	Type
withdrawals	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.createPayout.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.

GET /balance

Account balance

Detail	Value
Operation ID	igaming.getBalance
Method	GET
Path	/balance

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your NOWPayments connection from the Connection dropdown.
3. In the Operation dropdown, select igaming.getBalance.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream NOWPayments API reference.