API documentation
All documentation needed to integrate with Proxy-Seller lives at docs.proxy-seller.com. The summary below covers the parts that matter for security and procurement review.
Proxy services — get started
Register or log in to the dashboard and request an API key. All authorisations use a unique API key. Separate keys are generated for each Proxy-Seller product line; the documentation calls out the difference per endpoint.
Endpoint categories
- Actions with proxies — receiving, unloading, and other operations with IPs
- Order actions — generation, extension, and retrieval of order data
- Balance — account balance and credit operations
- Residential proxy — sheet setup, sub-packages, session control, and rotation settings
SDKs
Officially maintained client libraries cover the full API surface area:
- PHP — composer require proxy-seller/user-api-php (OOP client, all endpoints wrapped) · GitHub
- Node.js — npm i proxy-seller-user-api (async/await for every method) · GitHub
- Python — pip install proxy-seller-user-api (sync, single-class API) · GitHub
- Java — Maven Central: com.proxy-seller:proxy-seller-user-api:1.1 · GitHub
- Go — go get bitbucket.org/proxy-seller/userApiGolang · GitHub
Mobile CRM
Mobile CRM uses a separate authorisation flow. Documentation:
Support
For integration questions not answered in the documentation, contact support@proxy-seller.com.
