Reseller API Reference

The Reseller API is the Admin API’s mechanism — api_key plus action — scoped to what a reseller is allowed to touch: their own lines, devices, sub-resellers and credits. It is the right surface for billing systems and reseller dashboards, because the panel enforces the reseller’s limits on every call; your integration cannot accidentally reach beyond them.

It requires its own reseller-type API access code, created by an administrator under Access Codes. Authentication and conventions are identical to the API overview.

The 36 actions

Account

user_info · packages

Lines

get_lines · get_line · create_line · edit_line · delete_line · enable_line · disable_line

MAG devices

get_mags · get_mag · create_mag · edit_mag · delete_mag · enable_mag · disable_mag · convert_mag

Enigma2 devices

get_enigmas · get_enigma · create_enigma · edit_enigma · delete_enigma · enable_enigma · disable_enigma · convert_enigma

Sub-resellers

get_users · get_user · create_user · edit_user · delete_user · enable_user · disable_user · adjust_credits

Logs and live state

activity_logs · user_logs · live_connections

A typical billing flow

BASE="https://your-panel.com/YOUR_RESELLER_ACCESS_CODE"
KEY="YOUR_RESELLER_API_KEY"

# What packages can this reseller sell, and at what credit cost?
curl "$BASE/?api_key=$KEY&action=packages"

# Customer paid — create their line against a package
curl "$BASE/?api_key=$KEY&action=create_line&username=client01&password=Secret123&package=2"

# Customer lapsed — switch them off without deleting history
curl "$BASE/?api_key=$KEY&action=disable_line&id=42"

Credits are the currency of the whole flow: line creation draws from the reseller’s balance according to the package, and adjust_credits moves balance to a sub-reseller. Every movement is recorded in credit_logs on the Admin API side, attributed to the account that made it.

Serving end-user apps rather than resellers? That is the Xtream Codes API.