ARNPROXY

Export an existing connection list; does not create a list

POST/account/api/v1/residential/export

Authorization

AuthorizationBearer YOUR_ARNPROXY_API_KEY
Required permissionread + optional credentials
Acceptapplication/json
Content-Typeapplication/json

Parameters

NameTypeDescription
list_id
bodyRequired
integerOwned ARNPROXY connection-list record ID, not the supplier list ID.
format
bodyOptional
stringhost_port | host_port_user_pass | user_pass_host_port | uri. Credential-bearing formats need credentials permission. Also supports csv | custom.
Default: "host_port"
protocol
bodyOptional
stringhttp or socks5; controls the prefix only for uri output.
Default: "http"
offset
bodyOptional
integer0–9999, below the port count.
Default: 0
limit
bodyOptional
integer1–1000; default 100.
Default: 100
columns
bodyConditional
string[]CSV only: id, endpoint, ip, port, login, password. Default ["id","endpoint"]. Login/password require credentials permission.
template
bodyConditional
stringRequired for custom, at most 200 characters. %endpoint%, %ip%, %port%, %id%, %login%, %username%, %password%, %login_url%, %password_url%. Control characters and unknown placeholders are rejected.

Request body

Replace YOUR_/FROM_ placeholders with values from the relevant catalog, quote or scope. Examples leave consent false; only approve a real operation intentionally.

request.json
{
    "list_id": "YOUR_LIST_ID",
    "format": "host_port",
    "offset": 0,
    "limit": 10
}

Additional usage examples

IDs and prices are illustrative; use real values from the catalog and the same quote. JSON IDs and expected_total_minor must be numbers. Examples deliberately keep terms=false; submit terms=true only after explicit customer approval for the real paid operation.

CSV export

Choose CSV columns from id, endpoint, ip, port, login and password. Custom formats accept only the documented %...% tokens and never execute code. Credential-bearing output requires credentials permission. The content is returned inside JSON; your application saves it to a file.

application/json
{
    "list_id": 10001,
    "format": "csv",
    "columns": [
        "id",
        "endpoint"
    ],
    "protocol": "http",
    "offset": 0,
    "limit": 10
}

Custom connection format

Choose CSV columns from id, endpoint, ip, port, login and password. Custom formats accept only the documented %...% tokens and never execute code. Credential-bearing output requires credentials permission. The content is returned inside JSON; your application saves it to a file.

application/json
{
    "list_id": 10001,
    "format": "custom",
    "template": "http://%login_url%:%password_url%@%endpoint%",
    "protocol": "http",
    "offset": 0,
    "limit": 10
}

Request example

cURL
printf 'Authorization: Bearer %s\n' "$ARNPROXY_API_KEY" |
  curl --silent --show-error --header @- \
    --header 'Accept: application/json' \
    --connect-timeout 10 --max-time 30 \
    --request POST --header 'Content-Type: application/json' \
    --data-binary @request.json \
    'https://www.arnproxy.com/account/api/v1/residential/export'

Examples are not executed on this page. Keep the API key in a server-side environment variable; do not put real keys in URLs or browser code. Prepare request.json for POST examples.

Responses

200Success response
application/json
{
    "ok": true,
    "data": {
        "list_id": 30001,
        "package_id": 20001,
        "authentication": "login_password",
        "format": "host_port",
        "protocol": null,
        "items": [
            "res.arnproxy.com:10000"
        ],
        "count": 1,
        "next_offset": 1,
        "credentials_included": false,
        "snapshot": {
            "source": "arnproxy_records",
            "observed_at": "2030-01-01T12:00:00+00:00",
            "fresh": true,
            "max_age_seconds": 3600,
            "reason": null
        },
        "source": "arnproxy_records",
        "provider_requests": 0,
        "proxy_connections_tested": false,
        "session_targeting_applied": false
    },
    "meta": {
        "request_id": "000000000000000000000001",
        "phase": "public_v1",
        "source": "arnproxy_records"
    }
}
Response fields and types
NameTypeDescription
okbooleanSuccess envelope flag; on false inspect error.code.
dataobjectOperation-specific result; examples are illustrative and synthetic.
data.list_idintegerRelevant ARNPROXY record ID; use it instead of the upstream internal ID.
data.package_idintegerRelevant ARNPROXY record ID; use it instead of the upstream internal ID.
data.authenticationstringConnection list authentication mode: login_password or ip_auth.
data.formatstringOperation-specific format value; preserve its demonstrated type and consult the behavior notes.
data.protocolstring|nullOperation-specific protocol value; preserve its demonstrated type and consult the behavior notes.
data.itemsarrayRecords on this page or formatted connection strings; an empty list can be valid.
data.items[]stringRecords on this page or formatted connection strings; an empty list can be valid.
data.countintegerNumber of records visible in this result or generated connection strings.
data.next_offsetintegerNext connection-output offset, or null when complete.
data.credentials_includedbooleanWhether this result/key includes or permits sensitive credentials.
data.snapshotobjectPackage snapshot origin/time/freshness; stale snapshots do not grant management access.
data.snapshot.sourcestringData source; local records and a live provider lookup are different evidence.
data.snapshot.observed_atstringTimestamp in the API’s returned representation; example dates are synthetic.
data.snapshot.freshbooleanWhether the observation satisfies its freshness window.
data.snapshot.max_age_secondsintegerMaximum snapshot age allowed for freshness, in seconds.
data.snapshot.reasonstring|nullFixed reason code or null, never raw provider error text.
data.sourcestringData source; local records and a live provider lookup are different evidence.
data.provider_requestsintegerOperation-specific provider requests value; preserve its demonstrated type and consult the behavior notes.
data.proxy_connections_testedbooleanOperation-specific proxy connections tested value; preserve its demonstrated type and consult the behavior notes.
data.session_targeting_appliedbooleanOperation-specific session targeting applied value; preserve its demonstrated type and consult the behavior notes.
metaobjectRequest correlation and data-source metadata.
meta.request_idstringThis HTTP request’s correlation ID, not an operation key or order ID.
meta.phasestringOperation-specific phase value; preserve its demonstrated type and consult the behavior notes.
meta.sourcestringData source; local records and a live provider lookup are different evidence.

Error response

HTTP 401 · INVALID_API_KEY
{
  "ok": false,
  "error": { "code": "INVALID_API_KEY" },
  "meta": { "request_id": "000000000000000000000001" }
}

Authentication and validation may reject a request before execution. Consult the error reference and retain request_id when contacting support. Never send keys or passwords. Errors & limits →

Behavior & important notes

  • Package and list IDs are ARNPROXY record IDs, not upstream package keys or list IDs. A stale package snapshot cannot grant access; refresh it with residential_package_refresh when needed.
  • Credential-bearing output requires credentials permission. Never log or send returned connection strings, passwords or Authorization headers to support.

Search the current language. Close with Esc