Build 2extract into your product
Everything in the dashboard is in the public API: create a proxy for each of your users, set its limits and read its usage from your own code.
How an integration works
Your product talks to the API; your users' traffic goes through the 2extract gateway. Nothing else sits in between.
One proxy per user
Create a proxy for each of your users with POST /v1/proxy: its own password, targeting, IP whitelist and a daily or monthly limit in GB or USD, so one user never spends another's budget.
Hand your user the connection string. Country, city and session stay in the username, so your product can change them per request.
From an API key to your user's first request
Three steps, and your user is connected.
Create a scoped API key
Sign up, top up from $10 and create a key with
proxies:writeandstats:readunder API keys.Create a proxy for your user
POST /v1/proxywith a name, the product, targeting and a limit; the response carries the host, port and password.Hand over the connection string
Your user connects through the gateway with the proxy's credentials; read their usage with
GET /v1/proxy/{id}/usage/export.
# Replace with your credentials from the 2extract dashboard
curl --proxy "http://2xt-customer-[accountID]-proxy-[name]-[params]:proxy_password@proxy.2extract.net:5555" \
"https://api.ipify.org?format=json"What the API covers
Each API key carries only the scopes it needs. The same keys connect AI agents through the MCP server.
Open the API referenceProxies
Create, update and delete proxies; set targeting, IP and target-host whitelists; rotate passwords.
Limits
Cap each proxy daily or monthly, in GB of traffic or in USD of spend.
Usage you can reconcile
Account traffic for any date range, and a per-day CSV of traffic and spend for each proxy to check against your own numbers.
Balance
The current balance and the full transaction history.
Geo
The countries, states, cities and ZIP codes you can target.
Scoped keys
proxies, stats, balance and geo scopes, each granted on its own; a key is shown once and can be rotated.
Ready for anti‑detect browsers
Step-by-step guides for 27 anti-detect browsers. Every one connects through the same endpoint and the same username format.
A partner program for anti-detect browsers is coming. Tell us about your product.
Integration questions
Every endpoint, scope and error is in the API reference.
Still have a question?
Talk directly to the engineers who built the product. No chatbots, no first-level support scripts.
Your integration starts with one API key
Sign up with Google, GitHub or email, top up from $10 and create a scoped key in the dashboard.