Skip to main content

UnindexedApiError

Type Alias UnindexedApiError 

Source
pub type UnindexedApiError = ApiError<AssetNameExchange, InstrumentNameExchange>;
Expand description

Type alias for a ApiError that is keyed on AssetNameExchange and InstrumentNameExchange (yet to be indexed).

Aliased Type§

pub enum UnindexedApiError {
Show 13 variants AssetInvalid(AssetNameExchange, String), InstrumentInvalid(InstrumentNameExchange, String),
#[non_exhaustive]
RateLimit { retry_after: Option<Duration>, }, CapacityExceeded(String), Unauthenticated(String), BalanceInsufficient(Option<AssetNameExchange>, String), OrderRejected(String), OrderAlreadyCancelled, OrderAlreadyFullyFilled, OrderAlreadyExpired, DuplicateClientOrderId(String), RequestRejected(String), BorrowRejected(BorrowReject),
}

Variants§

§

AssetInvalid(AssetNameExchange, String)

Provided asset identifier is invalid or not supported.

For example:

Not transient — do not retry. The asset identifier must be corrected.

Indexed only when the ExecutionInstrumentMap holds the asset. Otherwise there is no index to carry, and AccountEventIndexer reports it as OrderRejected (from an order request) or RequestRejected (from any other request), holding this error’s own message.

§

InstrumentInvalid(InstrumentNameExchange, String)

Provided instrument identifier is invalid or not supported.

For example:

Not transient — do not retry. The instrument identifier must be corrected.

Indexed only when the ExecutionInstrumentMap holds the instrument; otherwise reported as AssetInvalid describes.

§

#[non_exhaustive]
RateLimit

Request was rejected due to rate limiting.

The exchange enforces request quotas and the caller has exceeded them. The client may already have waited and retried within its own bounded retries before surfacing this.

retry_after is the venue’s own minimum wait, measured from when the client read the refusal: do not retry sooner. None means the venue sent no hint, or the client cannot read it, and is not permission to retry at once. Which clients fill it:

  • Alpaca: from a 429’s Retry-After, or else X-RateLimit-Reset, once the client’s own retries are exhausted.
  • Binance: from a REST 429’s or 418’s Retry-After, or the time a WebSocket API refusal’s retryAfter names, measured against the local clock. Uncapped, since a ban can last days, so add it to an Instant with checked_add. A request the client held back unsent, because an earlier refusal’s wait had longer left than the client sleeps through, reports the time left.
  • Hyperliquid: never: its SDK keeps no headers, and Hyperliquid documents no hint.

A venue ban (Binance’s HTTP 418) is reported the same way: its hint, when readable, says how long it lasts.

Transient — retry after retry_after when given, otherwise with backoff.

The variant is #[non_exhaustive]: outside this crate, build one with ApiError::rate_limited, match it as RateLimit { .. }, and read the wait with ApiError::retry_after.

Fields

This variant is marked as non-exhaustive
Non-exhaustive enum variants could have additional fields added in future. Therefore, non-exhaustive enum variants cannot be constructed in external crates and cannot be matched against.
§retry_after: Option<Duration>
§

CapacityExceeded(String)

The venue refused because a cap on something held at once is full, such as IBKR’s market data lines, which every TWS session and API client on the account shares.

Unlike RateLimit, waiting does not clear it: releasing something does, such as cancelling another subscription, whether this client holds it or another session on the same account does. The message carries the venue’s words.

Not transient: the same request retried with backoff alone meets the same refusal while the cap stays full.

§

Unauthenticated(String)

Authentication failed (invalid credentials, expired key, bad signature).

Unlike other API errors which affect a single request, authentication failures indicate that all subsequent requests will fail until credentials are corrected. Callers should halt trading and alert operators.

Not transient — do not retry. Fix credentials and restart.

§

BalanceInsufficient(Option<AssetNameExchange>, String)

Balance of an asset is insufficient to execute the requested operation.

The asset is None when it is not known which asset ran short:

  • the venue’s rejection does not name it (e.g. Binance’s “Account has insufficient balance for requested action”, or any Hyperliquid margin or spot-balance refusal), and a client does not guess it from the order;
  • the venue named an asset that the ExecutionInstrumentMap does not hold, so it has no index. AccountEventIndexer::api_error logs the name it dropped.

The String carries the venue’s message.

Not transient — do not retry the same request. Reduce order size or deposit additional funds.

§

OrderRejected(String)

Order was rejected by the exchange for a business rule violation.

Common causes include: price outside allowed range, quantity below minimum, post-only order would cross, reduce-only with no position.

Not transient — do not retry the same request. Adjust order parameters.

§

OrderAlreadyCancelled

Cancel request failed because the order was already cancelled.

This is a state conflict, not an error per se — the desired end state (order cancelled) has already been achieved.

Not transient — do not retry. The order is already in the cancelled state.

§

OrderAlreadyFullyFilled

Cancel request failed because the order was already fully filled.

This is a state conflict — the order completed before the cancel arrived. The caller should reconcile their local state with the fill.

Not transient — do not retry. The order no longer exists to cancel.

§

OrderAlreadyExpired

Cancel request failed because the order had already expired.

This is a state conflict — the order’s own deadline retired it before the cancel arrived, so the desired end state (order no longer working) has already been achieved. Distinct from OrderAlreadyCancelled because nobody asked for it: a time-in-force such as GoodTillDate retired it unprompted, and a caller reconciling its local state needs to know which of the two happened.

Not transient — do not retry. The order no longer exists to cancel.

§

DuplicateClientOrderId(String)

Open request refused because its ClientOrderId is already in use at the venue.

The refusal concerns this request alone: the order already under the id is unaffected, and is not reported ended by it. What “in use” means is the venue’s rule. On the SimulatedVenue and the IBKR client it is an order still working under the id, and an id is free again once its order has ended. Binance documents an id as unique among open orders. The String carries the venue’s message, or the client’s own where it refused the request before sending it.

Reported by the SimulatedVenue, by the IBKR client, which refuses the request before it reaches TWS, since TWS never sees a client order id, and by the Binance spot and margin clients, from Binance’s "Duplicate order sent.". Other clients report a venue’s duplicate rejection as OrderRejected until its message has been confirmed.

Not transient — the same request fails identically while the order under the id works. Use another id, or wait for that order to end.

§

RequestRejected(String)

The exchange refused the request itself, rather than an order it carried.

The request was malformed or asked for something the venue does not serve — a missing, malformed or out-of-range parameter, such as a query time window longer than the venue allows. Distinct from OrderRejected, which is an order failing a business rule; this variant arises from queries and other non-order requests. The message carries the venue’s own error code where it provides one (e.g. -1127 ... on Binance).

Not transient — the same request fails identically on retry. Change the request.

§

BorrowRejected(BorrowReject)

Order refused because the venue would not lend what it needed: a short sale, or a margin order that borrows to cover itself.

Distinct from OrderRejected so a caller can tell a refused borrow apart from a malformed order, and from BalanceInsufficient, which is the account’s own funds running short. A borrow can be refused for a long too: on Binance margin, an order that borrows to buy is refused when the venue has too little of the asset to lend or the borrow would exceed the account’s limit. BorrowReject says why.

Reported by the Binance margin client, by Binance’s code, by the Alpaca client, by the text of a 403 or 422, and by the SimulatedVenue, for a CFD short its ShortabilityProvider does not allow. Other clients report such refusals as OrderRejected until their venue’s wording is confirmed.

Not transient — the same request fails identically until the venue’s lending changes.