ARNPROXY

Residential ISP identifiers

GET/account/api/v1/residential/isp-codes

Authorization

AuthorizationBearer YOUR_ARNPROXY_API_KEY
Required permissionread
Acceptapplication/json

Parameters

NameTypeDescription
q
queryOptional
stringISP-name search, up to 80 UTF-8 bytes; no control characters, < or >.
after_code
queryOptional
integerPrevious next_after_code; starts at 0.
Default: 0
limit
queryOptional
integer1–100; default 50.
Default: 50

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 \
    'https://www.arnproxy.com/account/api/v1/residential/isp-codes?q=Telecom&limit=25'

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": {
        "items": [
            {
                "id": 100,
                "name": "Example ISP"
            }
        ],
        "next_after_code": null,
        "source": "provider_read",
        "availability_guaranteed": false,
        "automatic_retry": false
    },
    "meta": {
        "request_id": "000000000000000000000001",
        "phase": "public_v1",
        "source": "provider_read"
    }
}
Response fields and types
NameTypeDescription
okbooleanSuccess envelope flag; on false inspect error.code.
dataobjectOperation-specific result; examples are illustrative and synthetic.
data.itemsarrayRecords on this page or formatted connection strings; an empty list can be valid.
data.items[]objectRecords on this page or formatted connection strings; an empty list can be valid.
data.items[].idintegerRelevant ARNPROXY record ID; use it instead of the upstream internal ID.
data.items[].namestringOperation-specific name value; preserve its demonstrated type and consult the behavior notes.
data.next_after_codeinteger|nullCursor for the next page; null means no further page in this result.
data.sourcestringData source; local records and a live provider lookup are different evidence.
data.availability_guaranteedbooleanOperation-specific availability guaranteed value; preserve its demonstrated type and consult the behavior notes.
data.automatic_retrybooleanOperation-specific automatic retry 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.

Search the current language. Close with Esc