Saved purchase result

GET/account/api/v1/orders/create/status

Authorization

Authorization	`Bearer YOUR_ARNPROXY_API_KEY`
Required permission	`read`
Accept	`application/json`
Idempotency-Key	16–100 letters, digits, _ or -. Persist and reuse the same value for the same operation.

Parameters

Name	Type	Description
`Idempotency-Key` headerRequired	`string`	16–100 letters/digits/_/-. Keep the same value for the operation/status; do not reuse with a different body.

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' \
    'https://www.arnproxy.com/account/api/v1/orders/create/status'

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": "accepted",
        "delivery_state_at_acceptance": "queued",
        "currency": "TRY",
        "total": "10.00",
        "total_minor": 1000,
        "checkout_group_id": null,
        "orders": [
            {
                "id": 10001,
                "number": "1000010001",
                "location_id": 10,
                "time_id": 101,
                "quantity": 1,
                "total": "10.00"
            }
        ],
        "accepted_at": "2030-01-01T12:00:00+00:00",
        "automatic_renewal": false,
        "replayed": 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.state`	`string`	Record/operation state. accepted is not delivery; completed is not a connection test.
`data.delivery_state_at_acceptance`	`string`	Operation-specific delivery state at acceptance value; preserve its demonstrated type and consult the behavior notes.
`data.currency`	`string`	Account transaction currency: TRY or USD.
`data.total`	`string`	Money amount; preserve the returned string/integer representation for precision.
`data.total_minor`	`integer`	Integer minor units: 1000 means 10.00 TRY/USD.
`data.checkout_group_id`	`integer\|null`	Operation-specific checkout group id value; preserve its demonstrated type and consult the behavior notes.
`data.orders`	`array`	Operation-specific orders value; preserve its demonstrated type and consult the behavior notes.
`data.orders[]`	`object`	Operation-specific orders value; preserve its demonstrated type and consult the behavior notes.
`data.orders[].id`	`integer`	Relevant ARNPROXY record ID; use it instead of the upstream internal ID.
`data.orders[].number`	`string`	Display order number; not interchangeable with fields requesting an id.
`data.orders[].location_id`	`integer`	Local catalog location or product-type ID.
`data.orders[].time_id`	`integer`	Local period/GB-plan record ID, not a day or GB count.
`data.orders[].quantity`	`integer`	Selected or ordered proxy quantity.
`data.orders[].total`	`string`	Money amount; preserve the returned string/integer representation for precision.
`data.accepted_at`	`string`	Timestamp in the API’s returned representation; example dates are synthetic.
`data.automatic_renewal`	`boolean`	Operation-specific automatic renewal value; preserve its demonstrated type and consult the behavior notes.
`data.replayed`	`boolean`	Saved result for the same operation was returned, not proof of a new debit/action.
`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 →