---
title: "Confirm Order Reply Message"
method: POST
path: "/iserver/reply/{replyId}"
tags: ["tradingOrders"]
---

# Confirm Order Reply Message

`POST /iserver/reply/{replyId}`

Confirm an order reply message and continue with submission of order ticket.

## Path parameters

- `replyId` string, required

## Request body

- object
  - `confirmed` boolean — Value of true answers the question in the affirmative and proceeds with order submission.

## Response `200`

Status of reply

- union
  - OrderSubmitSuccessItems[] — A successful submission of one or more order tickets.
    - `order_id` string — The order ID assigned to your order ticket by IB. Contains only numerals.
    - `order_status` string — Status describing where the order stands in its lifecycle.
    - `encrypt_message` string — Internal use only.
  - OrderReplyMessageItems[] — An array containing objects that each deliver the order reply messages emitted against one order ticket in the submission request's array. Indicies of the order reply message objects in this array correspond to the indicies of the order tickets in the submission request's array.
    - `id` string — The replyId UUID of the order ticket's emitted order reply messages, used to confirm them and proceed. Use the POST /iserver/reply/{replyId} endpoint to confirm an order reply message.
    - `isSuppressed` boolean — Internal use. Always delivers value 'false'.
    - `message` string[] — An array containing the human-readable text of all order reply messages emitted for the order ticket.
    - `messageIds` string[] — An array containing identifiers that categorize the types of order reply messages that have been emitted. Elements of this array are ordered so that indicies match the corresponding human-readable text strings in the 'message' array. A messageId can typically be passed in the POST /iserver/questions/suppress endpoint to auto-accept a given warning message.
  - OrderSubmitError — Indicates that the order reply message or submission was not accepted.
    - `error` string — Message indicating that order submission was not successful.
  - OrderReplyNotFound — Indicates that the order reply ID does not exist.
    - `error` string — Message indicating that order reply id was not found.
  - AdvancedOrderReject — Relates a message generated in response to the rejection of the submitted order ticket. In some cases, it may also present a mechanism to resubmit the same order following a prompted decision.
    - `orderId` integer — The order ID assigned by IB to the rejected order ticket.
    - `reqId` string — IB's internal identifier assigned to the returned message.
    - `dismissable` unknown[] — Indicates whether this prompt is dismissable.
      - unknown
    - `text` string — Human-readable text of the messages emitted by IB in response to order submission.
    - `options` string[] — Choices available to the client in response to the rejection message.
    - `type` string — The specific type of message returned.
    - `messageId` string — IB internal identifier for the nature or category of the returned message.
    - `prompt` boolean — Indicates that the message is a prompt offering a set of decisions, one or more of which may permit the rejected order to be resubmitted.

## Other responses

- `401` — Missing, invalid, or unparseable Authorization token.
- `500` — internal server error, returned when incoming request cannot be processed. It can sometimes include subset of bad requests. For example, wrong accountId passed and it can only be detected later in handling request. Error contains reason of the problem.
- `503` — service is unavailable. For example if request takes more than 10s due to some internal service unavailability, request aborted and this status returned

---

[API](https://skmtc.net/interactivebrokers/apis/api-reference.md) · [All operations](https://skmtc.net/interactivebrokers/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/interactivebrokers/api-reference/revisions/67f9f562c2c6/schema)