API

API, in the SMM panel sense, is the interface that lets a panel or buyer place and track orders on another panel automatically, using a key instead of the website's order form.

The common convention is a single endpoint that takes an API key and an action. The action says what you want: services returns the catalogue with service IDs, rates, minimums and maximums; add places an order with a service ID, a link and a quantity; status reports the order state, start count and remaining quantity; balance returns your funds; refill and cancel request those actions where the service supports them. Field names and extra actions vary between panels, so read the panel's API page rather than assuming.

An add request is accepted once three checks pass: the service exists, the quantity is between the minimum and maximum, and your balance covers the cost. The charge is taken at that moment. The link is generally taken as given. The panel does not open it to confirm it points at the right post or that the profile is public, so a typo, a wrong post or a private account usually becomes a charged order rather than an error. What happens next depends on the supplier: the order may be cancelled and refunded, or it may be delivered to whatever the link points at.

The key is the only thing that authorises an order. Anyone holding it can spend your balance, so treat it like a password, keep it out of shared code and regenerate it if it leaks. If you automate against a panel, store the order ID the add action returns, because that ID is what support asks for when something goes wrong.

What it does not mean

An API does not mean the panel produces the service. A panel offering an API may itself be forwarding each order through someone else's API, so the service you connect to can sit several steps away from whoever delivers it.