Proxy reseller API
A proxy reseller API is a set of HTTP endpoints your server calls to buy proxies for your customers, read their credentials and manage renewals. This guide walks through the NobleProxy reseller API and the patterns that keep an integration reliable.
Quick answer
A proxy reseller API lets your backend create proxy orders on demand and receive ready-to-use credentials in the response. The NobleProxy reseller API uses Bearer API keys and JSON at https://nobleproxy.com/api/v1, with endpoints for products, balance, orders, renewals, auto-renew and IP swaps.
A proxy reseller API is a set of HTTP endpoints your server calls to buy proxies for your customers, read their credentials and manage renewals. This guide walks through the NobleProxy reseller API and the patterns that keep an integration reliable.
A proxy reseller API lets your backend create proxy orders on demand and receive ready-to-use credentials in the response. The NobleProxy reseller API uses Bearer API keys and JSON at https://nobleproxy.com/api/v1, with endpoints for products, balance, orders, renewals, auto-renew and IP swaps.
| Base URL | https://nobleproxy.com/api/v1 |
|---|---|
| Authentication | Authorization: Bearer <API key> |
| Format | JSON; amounts in US cents |
| Catalog | GET /products |
| Balance | GET /balance |
| Orders | POST /orders, GET /orders, GET /orders/{id} |
| Lifecycle | PATCH /orders/{id}, POST /orders/{id}/renew, POST /orders/{id}/swap |
| Proxy format | HTTP proxy, host:port with username and password |
Dashboard, Reseller API, Create API key. Save it as a server environment variable.
Call GET /products every few minutes and cache types, countries and prices.
POST /orders with product, quantity, type and country, plus your order id as idempotencyKey.
Display host, port, username and password from the response or from GET /orders/{id}.
Use PATCH for auto-renew, POST renew for manual renewals and POST swap for new static IPs.
A 200 response with balanceCents means the key works.
A 401 response means the key is missing, mistyped or was replaced by a newer key.
Facts last reviewed 2026-11-07.
Everything a store needs to sell proxies without manual work. GET /products returns the catalog with prices, types and countries in stock. POST /orders buys static or rotating residential proxies and returns them. GET /orders and GET /orders/{id} list orders and show current credentials and expiry. PATCH /orders/{id} turns auto-renew on or off, POST /orders/{id}/renew renews now (rotating orders only while auto-renew is on), and POST /orders/{id}/swap replaces static IPs.
Create a key in the dashboard and send it as Authorization: Bearer on every request from your server. Keys are shown once and stored hashed. Every order and renewal is paid from your prepaid balance; if the balance is too low the API returns 402 and charges nothing, so your store can show a clear message.
Create supplier orders only after your customer's payment is confirmed. Send your own order id as idempotencyKey, so a network retry returns the first order instead of buying twice. Store the returned order id with your customer, read GET /orders/{id} when you show credentials, and handle 502 by retrying or offering another country or type, because nothing was charged.
Yes. There is no API fee. You pay only for the proxies you order, at public prices, from your balance.
Any language that can send HTTPS requests with JSON. The documentation includes curl, JavaScript and Python examples.
Credentials are returned in the POST /orders response. New static IPs can take a few minutes to start accepting connections.
No. Keep the key on your server and let your frontend talk to your own backend.
Yes. Add -cc- and a two-letter country code to the rotating proxy username, for example user-cc-us.
Pricing, products and how to join.
View pageUse the API behind your storefront.
View pageUse the API from a bot backend.
View pageKeep your brand in front of customers.
View pageBuy self-serve now, or talk with us about a larger agency inventory.