ARNPROXY

Explicitly resume only an unsent replacement step

POST/account/api/v1/extra-logins/replace/resume
Confirm the operation deliberately

This operation may change a record, balance or service configuration. Read its scope and notes first. After an uncertain result, query the same operation rather than starting another.

Authorization

AuthorizationBearer YOUR_ARNPROXY_API_KEY
Required permissionproxy_management
Acceptapplication/json
Content-Typeapplication/json
Idempotency-Key16–100 letters, digits, _ or -. Persist and reuse the same value for the same operation.

Parameters

NameTypeDescription
Idempotency-Key
headerRequired
string16–100 letters/digits/_/-. Keep the same value for the operation/status; do not reuse with a different body.
terms
bodyRequired
booleanMust be the JSON boolean true for explicit approval, not the string "true".

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
{
    "terms": false
}

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 \
    --header 'Idempotency-Key: YOUR_SAVED_OPERATION_KEY' \
    --request POST --header 'Content-Type: application/json' \
    --data-binary @request.json \
    'https://www.arnproxy.com/account/api/v1/extra-logins/replace/resume'

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": {
        "state": "completed",
        "phase": "done",
        "action": "replace_extra_login",
        "old_login_id": 40001,
        "new_login_id": 40002,
        "proxy_ids": [
            12345
        ],
        "reason_code": null,
        "resume_available": false,
        "replayed": true,
        "primary_credentials_modified": false,
        "credentials_included": false,
        "strategy": "create_verify_then_revoke_old"
    },
    "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.statestringRecord/operation state. accepted is not delivery; completed is not a connection test.
data.phasestringOperation-specific phase value; preserve its demonstrated type and consult the behavior notes.
data.actionstringOperation-specific action value; preserve its demonstrated type and consult the behavior notes.
data.old_login_idintegerRelevant ARNPROXY record ID; use it instead of the upstream internal ID.
data.new_login_idintegerRelevant ARNPROXY record ID; use it instead of the upstream internal ID.
data.proxy_idsarrayProxy IDs in the scope visible to this account.
data.proxy_ids[]integerProxy IDs in the scope visible to this account.
data.reason_codestring|nullFixed reason code or null, never raw provider error text.
data.resume_availablebooleanExplicit resume availability for an unsent step; do not auto-retry when false.
data.replayedbooleanSaved result for the same operation was returned, not proof of a new debit/action.
data.primary_credentials_modifiedbooleanOperation-specific primary credentials modified value; preserve its demonstrated type and consult the behavior notes.
data.credentials_includedbooleanWhether this result/key includes or permits sensitive credentials.
data.strategystringExtra-login replacement verifies new access before revoking the selected old access.
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

  • Extra logins are separate from the primary delivery login. Creating one does not replace the primary login or delete other extra logins. Read custom_credentials_available, username_length and password_length from the options response before creating credentials.
  • id is an extra-login ID, not a proxy ID. A new login is verified before only the selected old login is revoked. The primary proxy table is unchanged.
  • An action may apply to an entire authorization group, such as an order or package, rather than only the selected proxy. Review proxy_ids, authorization_scope and may_affect_other_proxies before continuing. Obtain a new revision if the scope changes.
  • A timeout/5xx is not proof that a write failed. Use the original Idempotency-Key with its status resource. Do not retry under a new key; GET does not resend the change.
Follow the same operationReconcile the same replacement; no provider writes →

Search the current language. Close with Esc