API and integration
Admin API
Last updated by The PanelCompare editorial team
Why does admin api matter to a buyer?
The two APIs answer different questions and only one of them is standardised. The user API is the near-universal v2 specification every panel implements, so a client written against one works against hundreds. The admin API is not standardised at all: it is whatever the panel software offers, and it is the reason a serious operator can reprice thousands of rows or repoint a provider in one call rather than by hand.
For a buyer the useful part is what its absence implies. A full user API plus an admin API, multi-currency, coupons and a child-panel product of its own is the feature signature of a main panel with its own infrastructure; child panels are typically stripped of the admin API and of the features that depend on it (PanelCompare domain research, 2026-09-06). That is inferable from the account area without believing a word of the marketing copy.
How does admin api show up in a price list?
It is documented, if at all, in a separate operator-facing page rather than on the public API page, and it is normally gated behind an admin login rather than an ordinary account key.
The buyer-visible proxy is the feature set it powers: bulk repricing, per-user custom rates, coupons, multi-currency and provider management all imply administrative tooling behind them.
Think this definition is wrong?
Terminology in this market is set by the panels that use it, and it moves. If a panel uses admin api 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.