SMM Panel API: Automate Orders with a Standard Action-Based API

If you place orders in bulk, run your own storefront or resell services to customers, doing it by hand does not scale. The EtkilesimBayim SMM panel API lets your own script or panel create orders, check their status and request refills automatically. It follows the standard action-based format that reseller panels commonly use, so many existing scripts and panel software can connect with little or no change.

Endpoint and Authentication

All requests go to a single endpoint: https://etkilesimbayim.com/api/v2. Send a POST request (form-encoded or JSON); a GET with the same parameters also works for connectivity checks. Every request needs two parameters: key (your API key) and action. You get your API key from your account page after you sign up. Responses are always JSON.

Supported Actions

Action	What it does	Parameters
services	Lists all active, visible services with price per 1,000, minimum and maximum quantity, type and cancel support	none
add	Creates an order and returns the order ID	service, link, quantity
status	Returns charge, start count, status and remaining quantity for one or many orders	order (comma-separated for several)
refill	Queues a refill request for review	order or orders (up to 100)
refill_status	Returns the status of a refill request	refill or refills (up to 100)
cancel	Requests cancellation for services that support it	orders (up to 100)
balance	Returns your current balance and currency	none

Example Request

Creating an order looks like this:

POST https://etkilesimbayim.com/api/v2
key=YOUR_API_KEY&action=add&service=1&link=https://instagram.com/example&quantity=1000

Response: { "order": 123 }

Order statuses returned by status are Pending, Processing, In progress, Completed, Partial, Canceled and Fail. Refill requests move through Pending, In progress, Completed or Rejected.

Error Handling

Errors are returned as HTTP 200 with a JSON body such as { "error": "Not enough funds" }, which is the convention most reseller scripts expect. Common messages include missing or invalid key, incorrect action, not enough funds and order not found. Your code should always check for an error field instead of relying on the HTTP status code.

Integration Tips

• Cache the service list. Call services periodically rather than before every order; prices and availability can change, so refresh it on a schedule.
• Poll status sensibly. Request many orders at once with comma-separated IDs instead of one call per order. Per-key rate limits apply, so avoid unnecessary polling.
• Handle partial and failed orders. Partial and Fail statuses should trigger your own follow-up, such as telling the customer or retrying.
• Refill and cancel are requests. Refill requests are queued for review and do not complete instantly. Cancel works only for services that report cancel: true.
• Protect your key. Keep it on the server side only, never in client-side code or public repositories.

Who Is the API For?

It suits anyone who wants to place orders programmatically: resellers who sell to their own customers, people who run a panel or storefront, and agencies that automate recurring campaigns. If you are comparing options before building on top of a provider, how to choose an SMM panel and how to start a reseller panel are good background reads. To resell under your own brand, see our reseller panel page. You can browse every service on the service and price list, or return to the SMM panel overview.

Full request and response details are in the API documentation. Create a free account to get your API key.