API v2

Balance, service sync, order creation and post-order actions from one endpoint.

Use the client API if you resell followers, likes, views and other SMM services from your own tools, website or bulk workflow.

balance services add status cancel refill refill_status
Endpoint https://zemiax.shop/api/v2 Sign in to reveal your client key.
API Workflow

Three things resellers usually need first

Stronger panel APIs do not need a long guide to get started. They need a clean endpoint, a valid key and a short path into orders, status and refill actions.

1. Authenticate Use your client key on every request

One key, one endpoint and the same action model across balance, services, add, status, cancel and refill.

2. Push orders Use the same catalog your account already sees

Resellers can automate against the same service IDs and rules the main order flow uses inside the panel.

3. Track and repeat Status, cancel and refill stay in the same API family

That makes repeat ordering and post-order handling much easier than juggling separate flows.

Quick start

POST endpoint
curl -X POST https://zemiax.shop/api/v2 \
  -d "key=YOUR_KEY" \
  -d "action=services"
Example add order
key=YOUR_KEY&action=add&service=123&link=https://example.com/post&quantity=1000

Your client key

Sign in to view your personal API key and start sending authenticated requests.

Actions

Main operations

The API mirrors the same service, order and refill flows the store uses, so resellers can automate without losing the main order logic.

Visible now 12 visible actions
Action Example
Balancekey=...&action=balance
Serviceskey=...&action=services
Addkey=...&action=add&service=123&link=https://...&quantity=100
Statuskey=...&action=status&order=999
Multi statuskey=...&action=status&orders=999,1000
Cancelkey=...&action=cancel&order=999
Multi cancelkey=...&action=cancel&orders=999,1000
Refillkey=...&action=refill&order=999
Multi refillkey=...&action=refill&orders=999,1000
Refill statuskey=...&action=refill_status&refill=123
Multi refill statuskey=...&action=refill_status&refills=123,124
SEO orderkey=...&action=add&service=123&link=https://...&quantity=1000&keywords=keyword1%0Akeyword2
Comment replieskey=...&action=add&service=123&link=https://...&username=example&comments=reply1%0Areply2
Reseller Path

API is only one part of reseller growth

The stronger public panels make API visible, but they also connect it to batch orders, referrals and child panels instead of treating docs as an isolated page.

Bulk Mass orders and repeat demand

Once the API is live, the next step is usually repeat batch volume instead of manual single-order work.

Referrals Push your own client acquisition

Referral links and repeat clients matter as much as raw API access if the goal is actual reseller growth.

Child panels Move strong buyers into their own panel later

That is usually where a simple buyer account becomes longer-term recurring revenue.