API and integration
Polling
Last updated by The PanelCompare editorial team
Why does polling matter to a buyer?
The absence of callbacks shapes every integration built on this market. There is no event when an order completes, none when it goes Partial, and none when a refill finishes; there is only the status action and the refill_status action, and whatever you last asked. Anyone reselling has to run a scheduler, decide an interval, and accept that the moment they learn about a failure is bounded by that interval rather than by when it happened.
It also makes bulk querying the only economical pattern. The multi-order form of status accepts up to 100 order IDs per request and returns an object keyed by ID, so a hundred orders cost one call rather than a hundred (verified against justanotherpanel.com/api, PanelCompare domain research, 2026-09-06). Polling one order at a time is what turns a reseller’s scheduler into something that looks, from the panel’s side, like abuse.
How does polling show up in a price list?
Nothing in a catalogue reflects it. What reflects it is how quickly a reseller’s own customers hear about a problem, which is a function of their polling interval rather than of the panel.
A comparison index polls for a different reason: calling the services and balance actions on a schedule is how availability and API latency are measured at all, and it is what detects a provider collapse days before a forum thread does.
Think this definition is wrong?
Terminology in this market is set by the panels that use it, and it moves. If a panel uses polling 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.