Skip to main content
The checkout endpoints cover buying: reading the catalog of what can be purchased, creating a hosted checkout session for a customer, and checking whether that session has settled. All requests go to https://api.nodemaven.com/api/v2/base/ and carry the header Authorization: x-api-key YOUR_API_KEY. See the NodeMaven API overview for the shared basics.

Endpoints

The catalog

GET /products returns what can be bought: traffic, subscriptions and ISP. Read the catalog from the API rather than hardcoding product identifiers, so your integration keeps working when the catalog changes.

Checkout is hosted

The checkout session is hosted. POST /checkout-sessions creates a session you send a customer to. It does not charge a card directly, so your integration never handles the payment itself. You pre-fill the session, hand it over, and the customer completes it.

CheckoutSessionCreate

The payment methods available through the API are the same ones NodeMaven accepts generally. See Payment methods for what each one covers, and Coupons for how the coupon field is used.

billing

ISPConfig

config uses ISPConfig, which applies when the session is for buying ISP proxies:
One checkout session can buy up to 100 ISP proxies. If a customer needs more than 100, create more than one session.

Polling a session

A checkout session does not settle the moment you create it, because the customer still has to complete it. GET /checkout-sessions/{id} is how you find out whether it has:
Poll it until it settles, then act on the outcome. If you would rather be notified than poll, see Webhooks for the events available on your account.