ARNPROXY

Read the existing customer-panel note of an owned active proxy

GET/account/api/v1/proxies/{id}/note

Authorization

AuthorizationBearer YOUR_ARNPROXY_API_KEY
Required permissionread
Acceptapplication/json

Parameters

NameTypeDescription
id
pathRequired
integerAn 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/proxies/YOUR_PROXY_ID/note'

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": {
        "proxy_id": 12345,
        "note": "Example label",
        "revision": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "note_update_available": true,
        "clear_with_empty_string": true,
        "source": "arnproxy_records",
        "maximum_length": 500,
        "maximum_utf8_bytes": 2000,
        "full_unicode_supported": true
    },
    "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.proxy_idintegerRelevant ARNPROXY record ID; use it instead of the upstream internal ID.
data.notestringOperation-specific note value; preserve its demonstrated type and consult the behavior notes.
data.revisionstringFreshness fingerprint to copy unchanged to the corresponding write/price confirmation.
data.note_update_availablebooleanOperation-specific note update available value; preserve its demonstrated type and consult the behavior notes.
data.clear_with_empty_stringbooleanOperation-specific clear with empty string value; preserve its demonstrated type and consult the behavior notes.
data.sourcestringData source; local records and a live provider lookup are different evidence.
data.maximum_lengthintegerOperation-specific maximum length value; preserve its demonstrated type and consult the behavior notes.
data.maximum_utf8_bytesintegerOperation-specific maximum utf8 bytes value; preserve its demonstrated type and consult the behavior notes.
data.full_unicode_supportedbooleanOperation-specific full unicode supported 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

  • Uses the existing customer-panel Proxy Note field; nothing is sent upstream. Up to 500 characters, subject to storage limits reported by GET. note="" clears it. Read proxy_note for a revision first. The same desired value returns changed:false; a different value cannot overwrite a stale revision. No Idempotency-Key is needed; re-read after an uncertain response.

Search the current language. Close with Esc