Common errors

Messages

MessageBaseOrderAmountTooSmallsource
Fields
MessageBaseOrderAmountTooLargesource
Fields
MessageQuoteOrderAmountTooSmallsource
Fields
MessageQuoteOrderAmountTooLargesource
Fields
MessagePriceTooSmallsource
Fields
MessageInsufficientBalancesource
Fields
MessageOrderIdNotExistsource
Fields
MessageMarketDoesNotExistsource
Fields
MessageMarketInMaintenanceModesource
Fields
MessageMarketInMaintenanceModeCancelOnlysource
Fields
MessageMarketClosedsource
Fields
MessageInvalidAmountPrecisionsource

Amount precision too high. For example, when placing an order for 0.3 satoshi when a market only allows you to buy/sell whole satoshi’s.

See also: What’s the supported price precision?

Fields
MessageInvalidPricePrecisionsource

price precision too high. For example, when attempting to place an order for 40.1 satoshi when the market only allows pricing in whole satoshi.

See also: What’s the supported price precision?

Fields
MessageTonceAlreadyUsedsource
Fields
MessageTonceTooNewsource
Fields
MessageTonceTooOldsource
Fields
MessageDeadlineExceededsource

Order was not accepted, due to an expired deadline. This may occur when an order is created with a deadline (time to live) timestamp in the past. Please also check if the time on the client is set correctly. Units returned are absolute timestamp since Unix epoch, in nanoseconds.

Fields
MessageValidateViolationsource
Fields
  • field (string) – A path leading to a field in the request message. The value is a sequence of dot-separated identifiers that identify a protocol buffer field. E.g., field_violations.field would identify this field.
  • value (string) – String representation of the value in error.
  • reason (string) – Reasoning of how the request element fails violation.