AxioAPI

Proxy API

List proxy locations, open sticky proxy sessions, rotate the exit node and close sessions when finished.

5 endpoints · 1 credit = $0.001. Each endpoint has its own credit cost, listed below. Calls that fail because of a service error are refunded.

API workspace and documentation

AxioAPI Studio · Proxy & VPN Nodes
Free Trial: 10 of 10 left

Type to search. A session can only be created for countries a proxy source supports.

  • Session lasts 24 hours
  • Rotate the IP any time within the session
  • Closing a session is free

No proxy session yet

Pick a country and create a session. You get the server, port and a ready-to-run connection command.

What you can build with the proxy API

The proxy API manages a proxy session from code: list locations, create a rotating or sticky session, rotate the exit node and close it when you are done. Use sticky sessions when a flow needs the same IP and rotation when it does not.

Keep one IP across a multi-step flow

Open a sticky session for a login, pagination or checkout sequence where the IP must stay the same.

POST /api/v1/proxy/sessions

Test content by location

List supported locations and open a session for a country to check how a page or service behaves there.

GET /api/v1/proxy/locations

Replace a node that stopped working

Rotate the exit node of an existing session instead of creating a new session from scratch.

POST /api/v1/proxy/sessions/{session}/rotate

Guides: Sticky vs rotating proxy: which one to use

How the proxy API works

  1. 1

    Choose a location

    GET /api/v1/proxy/locations lists supported countries and regions.

  2. 2

    Create a session

    POST /api/v1/proxy/sessions with a country, protocol (https, http, socks5, socks5h) and mode (rotating or sticky). Keep the session ID.

  3. 3

    Rotate and close

    POST .../sessions/{session}/rotate changes the exit node; DELETE .../sessions/{session} closes the session.

Try the Proxy & VPN Nodes API with your own account

New accounts receive 200 credits after verification, enough for about 2000 calls to "List proxy locations".

Using Proxy & VPN Nodes

List locations and choose a supported country and protocol before creating a session.

Keep the returned session ID for read, rotate and close operations. Treat proxy credentials as secrets.

To verify an exit IP, send a request through the supplied proxy. A session record alone does not prove traffic was routed.

Proxy API endpoints and pricing

OpenAPI 3.1 JSON

Select an operation above and open API & Docs for parameters and cURL, JavaScript, Python or PHP examples. The web tool uses your signed-in session; external integrations use a Bearer API key.

Method Endpoint Cost
GET List proxy locations /api/v1/proxy/locations
Helpful?
0.1 credit / request≈ $0.0001
POST Create proxy session /api/v1/proxy/sessions
Helpful?
2 credit / session≈ $0.002
GET Get proxy session /api/v1/proxy/sessions/{session}
Helpful?
0 credit / request
POST Rotate proxy node /api/v1/proxy/sessions/{session}/rotate
Helpful?
1 credit / request≈ $0.001
DELETE Close proxy session /api/v1/proxy/sessions/{session}
Helpful?
0 credit / request

Proxy API: frequently asked questions

What is the proxy API?

It manages a proxy session through REST: a sticky session keeps one IP, a rotating proxy changes the exit node, and every proxy session is created, rotated and closed with an API call.

What is the difference between sticky and rotating?

A sticky session keeps the same IP for the session, which suits logins and multi-page flows. A rotating session changes the exit node, which suits independent requests.

Which protocols are supported?

https, http, socks5 and socks5h are accepted when you create a session.

How do I confirm traffic goes through the proxy?

Send a request through the proxy details returned by the session and check the IP seen by the target. A session record alone does not prove traffic was routed.

How should I handle proxy credentials?

Treat them as secrets: do not log them or commit them to source control.

How is it billed?

Per session created and per rotation. Reading and closing a session are free. See the endpoint table below. New accounts receive 200 credits after verification.

Before integrating

Live and example data

Check the Live or Sandbox label before running. Examples demonstrate the response structure and do not guarantee live service status.

Credits and limits

Pricing depends on the endpoint and billable units. Failed live requests are not replaced with billable examples. Check your account limits before running repeated requests.

View pricing

Handling errors

Keep the request ID for troubleshooting. For 429, respect Retry-After when provided. If a create or delete request loses its connection, check the resource state before retrying.

Ready to integrate the Proxy & VPN Nodes API? Create an account and get your API key in minutes.