SMM Panel API
Standard protocol, so whatever you already built keeps working.
If you have integrated with an SMM panel before, you already know this API. It follows the same protocol every major panel uses — one POST endpoint, an action parameter, and your key. Client libraries, WooCommerce plugins and reseller panels written for another provider work here without changes.
What is worth knowing is how the money behaves through the API, because that is where panels differ. Order status returns the amount you have actually paid — the original charge minus any refunds — rather than the original charge. A partially delivered order refunds the undelivered portion to your balance automatically, so the number your system reads back is the true cost.
Errors return HTTP 200 with an error key in the body, which is what existing SMM clients expect. Check the body, not the status code.
Why order here
How it works
Email or Google. Takes under a minute, no card needed.
FPX online banking or DuitNow QR through toyyibPay — credited automatically once the bank confirms. USDT (TRC20) works too. Bank transfer can still be arranged over WhatsApp.
Pick the service, paste the post or profile link, choose a quantity. The price is shown before you confirm.
Track progress in the panel. Anything not delivered is refunded to your balance automatically.
Questions people ask
Is your API compatible with Perfect Panel?
Yes. Same endpoint shape, same action names, same response format. If your client works with a Perfect Panel provider, changing the URL and key is all that is needed.
Does charge in the status response include refunds?
Yes — it returns what you have actually paid, which is the original charge minus anything refunded. That is deliberate, so your accounting matches ours without a reconciliation step.
How do I handle partial delivery?
You do not have to. The undelivered portion is refunded to your balance automatically and the status response reflects the reduced charge. Read remains if you want to know how much was short.
Are service IDs stable?
Yes. Our service IDs are our own and stay fixed even when our supplier renumbers theirs. Do not hard-code them across providers though — pull the service list.
What rate limits apply?
300 requests per minute per API key. Exceeding it returns an error in the body rather than a 429, in line with the rest of the protocol.