Orders and statuses
Order error
Last updated by The PanelCompare editorial team
Why does order error matter to a buyer?
The HTTP behaviour is the single most consequential quirk in the specification. Errors return status 200 with a body such as an error field reading “Incorrect request”, so response codes carry no information and every integration must parse the body (verified against justanotherpanel.com/api, PanelCompare domain research, 2026-09-06). A script that trusts res.ok will happily report a hundred rejected orders as placed. One large panel additionally answers a bad key with HTTP 401 and a JSON error body, so a 4xx has to be parsed too rather than treated as “no API here”.
For a buyer ordering by hand the errors are narrower and mostly self-inflicted: a link in the wrong shape for the service, a quantity below the minimum or above the maximum, insufficient wallet balance, or a row the panel has disabled since the catalogue was last loaded. The last of these is worth noticing, because a headline rate that becomes unavailable the moment the wallet is funded is a bait-and-switch rather than an outage.
How does order error show up in a price list?
Errors do not appear in a catalogue; they appear at submission. The catalogue’s min, max and type fields are what determine most of them, which is why reading those three columns before ordering prevents most rejections.
On a mass order the whole batch is usually validated and priced before you confirm, so a single malformed line is caught early — but a batch that passes validation submits as one action, and the cancel window then applies to all of it at once.
Think this definition is wrong?
Terminology in this market is set by the panels that use it, and it moves. If a panel uses order error to mean something other than what is written here, send us the listing and we will either correct the definition or record the variant. The process is on the about page.