One package; stored snapshot

GET/account/api/v1/residential/packages/{id}

Authorization

Authorization	`Bearer YOUR_ARNPROXY_API_KEY`
Required permission	`read`
Accept	`application/json`

Parameters

Name	Type	Description
`id` pathRequired	`integer`	An owned record ID for this operation; 1–2147483647. Not a display order number or supplier ID.

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/packages/YOUR_PACKAGE_ID'

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": {
        "id": 20001,
        "state": "active",
        "snapshot": {
            "source": "arnproxy_records",
            "observed_at": "2030-01-01T12:00:00+00:00",
            "fresh": true,
            "max_age_seconds": 3600,
            "reason": null
        },
        "traffic": {
            "limit_bytes": "10737418240",
            "used_bytes": "1073741824",
            "remaining_bytes": "9663676416"
        },
        "expires_at": "2030-02-01T20:59:59+00:00",
        "rotation_seconds": 0,
        "management_available": false,
        "topup_available": true
    },
    "meta": {
        "request_id": "000000000000000000000001",
        "phase": "public_v1",
        "source": "arnproxy_records"
    }
}

Response fields and types

Name	Type	Description
`ok`	`boolean`	Success envelope flag; on false inspect error.code.
`data`	`object`	Operation-specific result; examples are illustrative and synthetic.
`data.id`	`integer`	Relevant ARNPROXY record ID; use it instead of the upstream internal ID.
`data.state`	`string`	Record/operation state. accepted is not delivery; completed is not a connection test.
`data.snapshot`	`object`	Package snapshot origin/time/freshness; stale snapshots do not grant management access.
`data.snapshot.source`	`string`	Data source; local records and a live provider lookup are different evidence.
`data.snapshot.observed_at`	`string`	Timestamp in the API’s returned representation; example dates are synthetic.
`data.snapshot.fresh`	`boolean`	Whether the observation satisfies its freshness window.
`data.snapshot.max_age_seconds`	`integer`	Maximum snapshot age allowed for freshness, in seconds.
`data.snapshot.reason`	`string\|null`	Fixed reason code or null, never raw provider error text.
`data.traffic`	`object`	Operation-specific traffic value; preserve its demonstrated type and consult the behavior notes.
`data.traffic.limit_bytes`	`string`	Byte count as a decimal string; avoid precision loss when converting to JavaScript Number.
`data.traffic.used_bytes`	`string`	Byte count as a decimal string; avoid precision loss when converting to JavaScript Number.
`data.traffic.remaining_bytes`	`string`	Byte count as a decimal string; avoid precision loss when converting to JavaScript Number.
`data.expires_at`	`string`	Operation-specific expires at value; preserve its demonstrated type and consult the behavior notes.
`data.rotation_seconds`	`integer`	Recorded/requested rotation in seconds; Rotating packages and Residential lists have different rules.
`data.management_available`	`boolean`	Availability under the result’s conditions/permissions, not a stock or provider guarantee.
`data.topup_available`	`boolean`	Operation-specific topup available value; preserve its demonstrated type and consult the behavior notes.
`meta`	`object`	Request correlation and data-source metadata.
`meta.request_id`	`string`	This HTTP request’s correlation ID, not an operation key or order ID.
`meta.phase`	`string`	Operation-specific phase value; preserve its demonstrated type and consult the behavior notes.
`meta.source`	`string`	Data 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.