MagnusBilling.net · API

API Dokumentation

Dokumentation der Kunden-API und Reseller-API

MagnusBilling.net · Client API

Client API Documentation

Manage your own SIP accounts, balance, vouchers, tariff plan, Caller ID, call history, refill history and account password through a clean JSON API.

Base URL https://magnusbilling.net/client-api/index.php
Authorization X-API-Key header
Response format JSON

Authorization

Every request must include your API key in the HTTP header.

X-API-Key: YOUR_API_KEY
Do not send the API key in the URL. Keep it private.

Account status

GET ?endpoint=me
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/client-api/index.php?endpoint=me"
{
  "success": true,
  "data": {
    "id": 1001,
    "username": "1234567801",
    "balance": "1.0000",
    "active": 1,
    "id_plan": 101,
    "plan_name": "STANDARD-PLAN"
  }
}

Balance

GET ?endpoint=balance
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/client-api/index.php?endpoint=balance"

Available plans

GET ?endpoint=plans

Returns only tariff plans available to your account.

curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/client-api/index.php?endpoint=plans"
You can choose only from the plans returned by this endpoint.

Change plan

POST ?endpoint=change-plan

Change your tariff plan to one of the available plans.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id_plan":8}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=change-plan"
You cannot create, edit or delete tariff plans through this API.

SIP accounts

GET ?endpoint=sip

List your SIP accounts, including SIP login and SIP password.

curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/client-api/index.php?endpoint=sip"

Create additional SIP account

POST ?endpoint=create-sip

Create an additional SIP account under your own account.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=create-sip"

You can also provide your own SIP password:

{
  "password": "StrongSipPass123"
}
Limit: maximum 100 SIP accounts per client.

Change SIP password

POST ?endpoint=update-sip-password
curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"1234567802","password":"NewSipPass456"}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=update-sip-password"
You can change only your own SIP accounts.

Delete SIP account

POST ?endpoint=delete-sip
curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"1234567802"}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=delete-sip"
The main SIP account cannot be deleted. Only additional SIP accounts can be deleted.

IP Authentication

Manage IP-based SIP authentication for your own SIP accounts. Your regular SIP login/password continues working.

List IP authorizations

GET ?endpoint=ip-auth-list

List your SIP accounts and active/inactive IP-auth records.

curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/client-api/index.php?endpoint=ip-auth-list"

Create IP authorization

POST ?endpoint=ip-auth-create

Add a public static PBX IP address to one of your SIP accounts.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sip_login":"1234567801","ip":"203.0.113.10"}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=ip-auth-create"
{
  "success": true,
  "message": "IP authentication created",
  "data": {
    "id": 6,
    "sip_login": "1234567801",
    "peer_name": "1234567801_ipa1",
    "ip": "203.0.113.10",
    "port": 5060,
    "status": 1
  }
}

Disable IP authorization

POST ?endpoint=ip-auth-disable

The IP-auth record stays in your account but becomes inactive. The SIP peer is removed from Asterisk.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id":6}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=ip-auth-disable"

Enable IP authorization

POST ?endpoint=ip-auth-enable

Re-enable a previously disabled IP-auth record.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id":6}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=ip-auth-enable"

Delete IP authorization

POST ?endpoint=ip-auth-delete

Delete the IP-auth record permanently.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id":6}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=ip-auth-delete"
IP authentication works only with a public static IPv4 address. Private or local IP addresses are rejected.
The same public IP cannot be active on two different client accounts at the same time.

Caller ID

GET ?endpoint=callerids
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/client-api/index.php?endpoint=callerids"

Add Caller ID

POST ?endpoint=add-callerid
curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"cid":"+1234567890","name":"Main Caller ID","set_active":true}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=add-callerid"

Set existing Caller ID as active

POST ?endpoint=set-callerid
{
  "cid": "+1234567890"
}

Delete Caller ID

POST ?endpoint=delete-callerid
{
  "id": 80
}

Clear active SIP Caller ID

POST ?endpoint=clear-callerid
curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=clear-callerid"

Call history

GET ?endpoint=calls&limit=50&offset=0
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/client-api/index.php?endpoint=calls&limit=50&offset=0"
Maximum limit per request: 200.

Refill history

GET ?endpoint=refills&limit=50&offset=0
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/client-api/index.php?endpoint=refills&limit=50&offset=0"

Redeem voucher

POST ?endpoint=redeem-voucher

Redeem an existing voucher code and add its value to your balance.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"voucher":"123456"}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=redeem-voucher"
This API does not create vouchers. It only redeems vouchers that already exist.

Change account password

POST ?endpoint=change-password
curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"current_password":"OldPassword","new_password":"NewPassword987"}' \
  "https://magnusbilling.net/client-api/index.php?endpoint=change-password"
The old account password is never returned by the API. It can only be changed.

SMS API / CryptoSMS

Senden Sie SMS über Ihr MagnusBilling-Konto mit demselben X-API-Key. Die Kosten werden vom Kontoguthaben abgezogen.

Basis-URL https://magnusbilling.net/sms-api/index.php
Öffentlicher Anbieter cryptosms / CryptoSMS

Autorisierung

Verwenden Sie denselben API-Schlüssel wie für Client API oder Reseller API.

X-API-Key: YOUR_API_KEY
Hinweis zu Sender ID / Caller ID
Sender ID / Caller ID wird nicht garantiert. Der angezeigte Absender hängt vom Anbieter, Zielland und den Regeln des Mobilfunkbetreibers ab.
Die SMS-Gebühr wird für den Sendeversuch berechnet. Die endgültige Zustellung hängt vom Mobilfunkbetreiber ab.

Endpoints

  • GET ?endpoint=providers — Anbieter anzeigen
  • GET ?endpoint=rates — SMS-Tarife
  • GET ?endpoint=quota&provider=cryptosms — SMS-Verfügbarkeit
  • POST ?endpoint=send — SMS senden
  • POST ?endpoint=schedule — SMS planen
  • GET ?endpoint=scheduled&limit=20 — Geplante SMS anzeigen
  • POST ?endpoint=cancel-scheduled — Geplante SMS abbrechen
  • POST ?endpoint=bulk — Bulk-SMS-Kampagne
  • GET ?endpoint=campaigns&limit=20 — Bulk-Kampagnen anzeigen
  • POST ?endpoint=cancel-campaign — Bulk-Kampagne abbrechen
  • GET ?endpoint=status&id=SMS_ID — SMS-Status prüfen
  • GET ?endpoint=history&limit=20 — SMS-Verlauf

SMS senden

POST ?endpoint=send
curl -k -sS \
  -X POST "https://magnusbilling.net/sms-api/index.php?endpoint=send" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "+447575396991",
    "provider": "cryptosms",
    "sender_id": "MyBrand",
    "message": "MyBrand: Your code is 123456"
  }'
{
  "success": true,
  "sms_id": 1,
  "provider": "cryptosms",
  "provider_name": "CryptoSMS",
  "status": "SENT_TO_PROVIDER",
  "balance_after": "49.6500",
  "sender_id": {
    "requested": "MyBrand",
    "guaranteed": false,
    "warning": "Sender ID / Caller ID is not guaranteed."
  }
}

SMS planen

POST ?endpoint=schedule
curl -k -sS \
  -X POST "https://magnusbilling.net/sms-api/index.php?endpoint=schedule" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "+1234567890",
    "provider": "cryptosms",
    "sender_id": "MyBrand",
    "message": "API scheduled test",
    "scheduled_at": "2026-05-09 23:00:00"
  }'
{
  "success": true,
  "scheduled_sms_id": 10,
  "provider": "cryptosms",
  "status": "SCHEDULED",
  "server_utc_offset": "+03:00"
}

Geplante SMS abbrechen

POST ?endpoint=cancel-scheduled
curl -k -sS \
  -X POST "https://magnusbilling.net/sms-api/index.php?endpoint=cancel-scheduled" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"scheduled_sms_id":10}'

Bulk-SMS-Kampagne

POST ?endpoint=bulk
curl -k -sS \
  -X POST "https://magnusbilling.net/sms-api/index.php?endpoint=bulk" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "cryptosms",
    "sender_id": "MyBrand",
    "message": "API bulk test",
    "scheduled_at": "2026-05-09 23:00:00",
    "phones": ["+1234567890", "+1234567891"]
  }'
{
  "success": true,
  "campaign_id": 20,
  "recipients_queued": 2,
  "status": "QUEUED"
}

Bulk-Kampagnen anzeigen

GET ?endpoint=campaigns&limit=20
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/sms-api/index.php?endpoint=campaigns&limit=20"

Bulk-Kampagne abbrechen

POST ?endpoint=cancel-campaign
curl -k -sS \
  -X POST "https://magnusbilling.net/sms-api/index.php?endpoint=cancel-campaign" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"campaign_id":20}'

SMS-Status prüfen

GET ?endpoint=status&id=SMS_ID
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/sms-api/index.php?endpoint=status&id=1"

SMS-Verlauf

GET ?endpoint=history&limit=20
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/sms-api/index.php?endpoint=history&limit=20"

eSIM API / Globale Datenpakete

Verkaufen Sie eSIM-Datenpakete über Ihr MagnusBilling.net-Konto mit demselben X-API-Key.

Base URL https://magnusbilling.net/esim-api/index.php

Authorization

Use the same API key that is already used for Client API or Reseller API.

Endpoints

  • GET ?endpoint=packages&q=Europe&limit=20 — List packages and current prices
  • GET ?endpoint=coverage&package_code=PACKAGE_CODE — Package coverage by country and network
  • GET ?endpoint=balance — Account balance
  • POST ?endpoint=buy — Buy eSIM package
  • GET ?endpoint=orders — Order history, QR/activation data and usage
  • GET ?endpoint=sync-order&order_id=ORDER_ID — Refresh order, QR and data usage

List packages

curl -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/esim-api/index.php?endpoint=packages&q=Europe&limit=5"

Buy eSIM

curl -sS -X POST "https://magnusbilling.net/esim-api/index.php?endpoint=buy" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{"package_code":"P2CYMUS93"}'

Orders and usage

curl -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/esim-api/index.php?endpoint=orders"

Security rules

  • The client can access only their own account.
  • The client can access only their own SIP accounts.
  • The client can manage IP authentication only for their own SIP accounts.
  • The client can add, change and delete only their own Caller IDs.
  • The client can choose tariff plan only from the available plan list.
  • The client cannot create, edit or delete tariff plans.
  • The client can redeem only existing voucher codes.
  • The client cannot delete the main SIP account.
  • The client cannot manage other clients, resellers or admin data.
MagnusBilling.net · Reseller API

Reseller API Documentation

Create SIP clients, manage balances, view reseller plans, check client status, and control customers through a clean JSON API.

Base URL https://magnusbilling.net/reseller-api/index.php
Authorization X-API-Key header
Response format JSON

Authorization

Every request must include your API key in the HTTP header.

X-API-Key: YOUR_API_KEY
Do not send the API key in the URL. Keep it private.

Account status

GET ?endpoint=me
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=me"
{
  "ok": true,
  "reseller": {
    "id": 1001,
    "username": "1234567890",
    "group": "Agent",
    "balance": 1,
    "active": true
  }
}

Plans

GET ?endpoint=plans
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=plans"
{
  "ok": true,
  "plans": [
    {
      "id": 33,
      "name": "TEST-RESELLER-PLAN",
      "signup": true,
      "initial_credit": 0,
      "tariff_limit": 3,
      "agent_rates": 66875
    }
  ]
}

Create client

POST ?endpoint=create-client

Create a new SIP client under your reseller account.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"plan_id":101}' \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=create-client"

You can also provide your own login and password:

{
  "login": "1234567891",
  "password": "StrongPass123",
  "plan_id": 101
}
SIP password is returned only once during client creation.
Ohne plan_id nutzt die API den bestehenden Retail-Client-Plan des Resellers. Standardpreise basieren auf dem Reseller-Basistarif mit 20% Aufschlag.

Get client

GET ?endpoint=client&login=LOGIN
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=client&login=1234567892"

Client list

GET ?endpoint=clients&limit=10&offset=0
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=clients&limit=10&offset=0"

Echtes Reseller-Abrechnungsmodell

Der transfer-Endpoint schreibt einem eigenen Kunden des Resellers Retail-Guthaben gut. Der Reseller wird nicht sofort belastet.

Standardmäßig werden Reseller-Kundentarife mit +20% Aufschlag erstellt. Der Reseller kann Aufschlag und Retail-Preise für eigene Kunden ändern.

Bei Anrufen wird das Kundenguthaben zum Retail-Tarif belastet, während das Reseller-Guthaben zum Wholesale-Tarif belastet wird.

Wenn das Wholesale-Guthaben des Resellers aufgebraucht oder für den Mindestabrechnungsblock nicht ausreichend ist, können Reseller-Kunden trotz Retail-Guthaben nicht telefonieren.

Retail-Guthaben gutschreiben

POST ?endpoint=transfer

Schreibt einem eigenen Kunden des Resellers Retail-Guthaben gut. Dies belastet den Reseller nicht sofort; das Wholesale-Guthaben wird erst bei Anrufen belastet.

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"login":"1234567892","amount":1,"external_id":"ORDER-DEMO-10001"}' \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=transfer"
external_id muss für jede Retail-Gutschrift eindeutig sein.

Transactions

GET ?endpoint=transactions
curl -k -sS \
  -H "X-API-Key: YOUR_API_KEY" \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=transactions&limit=10&offset=0"

Filter only successful transactions:

https://magnusbilling.net/reseller-api/index.php?endpoint=transactions&status=success&limit=10&offset=0

Set client status

POST ?endpoint=set-client-status

Deactivate client:

curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"login":"1234567892","active":false}' \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=set-client-status"

Activate client:

{
  "login": "1234567892",
  "active": true
}

Change client plan

POST ?endpoint=change-plan
curl -k -sS \
  -X POST \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"login":"1234567892","plan_id":101}' \
  "https://magnusbilling.net/reseller-api/index.php?endpoint=change-plan"

White-Label Agent Portal API

Endpoints für vom Agenten gehostete PHP-Portale: Client-Login, Dashboard, SIP, Anrufe, Zahlungen, Tarife, Aufschlag und Web-Phone-Token.

Für Reseller-Portale auf eigener Domain. Das Portal nutzt nur den reseller X-API-Key und verbindet sich niemals direkt mit der zentralen MagnusBilling-Datenbank.
Base URL https://magnusbilling.net/reseller-api/index.php
Authorization X-API-Key: YOUR_RESELLER_API_KEY

Client-Portal Endpoints

  • GET ?endpoint=portal-bootstrap — API-/Installationsprüfung
  • POST ?endpoint=client-auth — Client-Login im Agentenportal
  • GET ?endpoint=client-dashboard&login=CLIENT_LOGIN — Client-Dashboard und sichtbares Guthaben
  • GET ?endpoint=client-sip&login=CLIENT_LOGIN — Client-SIP-Konten; Service-Konten standardmäßig versteckt
  • GET ?endpoint=client-calls&login=CLIENT_LOGIN&limit=50 — Erfolgreiche Anrufe
  • GET ?endpoint=client-failed-calls&login=CLIENT_LOGIN&limit=50 — Fehlgeschlagene Anrufe
  • GET ?endpoint=client-refills&login=CLIENT_LOGIN&limit=50 — Aufladehistorie des Clients
  • GET ?endpoint=client-callerids&login=CLIENT_LOGIN — Caller ID des Clients
  • GET ?endpoint=client-rates&login=CLIENT_LOGIN&limit=100 — Retail-Tarife des Clients

Zahlung/Aufladung

Kundenzahlungen werden im Portal über Plisio, Heleket oder Custom-Methoden empfangen. Nach Bestätigung ruft das Portal register-agent-payment auf.

curl -sS -X POST "https://magnusbilling.net/reseller-api/index.php?endpoint=register-agent-payment" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "login": "CLIENT_LOGIN",
    "amount": "20.00",
    "currency": "EUR",
    "provider": "plisio",
    "external_id": "plisio_order_123",
    "provider_txid": "tx_or_invoice_id",
    "status": "paid"
  }'

Tarifaufschlag Endpoints

set-agent-markup nutzt den bestehenden Retail-Plan. Ist der Aufschlag bereits aktiv, werden Tarifzeilen nicht neu geschrieben.

  • GET ?endpoint=agent-markup — Aktueller Aufschlag und Retail-Tarif
  • POST ?endpoint=preview-agent-markup — Preisvorschau mit neuem Aufschlag
  • POST ?endpoint=set-agent-markup — Neuen Aufschlag auf Retail-Tarif anwenden
curl -sS -X POST "https://magnusbilling.net/reseller-api/index.php?endpoint=set-agent-markup" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"markup_percent":50}'

Janus Web Phone Token

Das Portal zeigt einen Web Phone Button. Service-SIP-Konten wie _web1 werden intern von Janus verwendet und nicht in der normalen SIP-Liste angezeigt, außer include_service=1.

curl -sS -X POST "https://magnusbilling.net/reseller-api/index.php?endpoint=client-softphone-token" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"login":"CLIENT_LOGIN"}'
White-Label Sicherheitsregeln: Endkunden dürfen Reseller-Guthaben, Wholesale-Kosten, Aufschlag, interne Kreditabhängigkeit, API-Key oder zentrale DB-Details nie sehen.

Reseller SMS API / CryptoSMS

Reseller können SMS für eigene Kunden mit demselben Reseller X-API-Key senden. client_login ist erforderlich.

Basis-URL https://magnusbilling.net/sms-api/index.php
Autorisierung X-API-Key: YOUR_RESELLER_API_KEY
Für Reseller erforderlich client_login muss der Login Ihres eigenen Kunden sein.
Ein Reseller kann SMS nur für eigene Kunden verwalten.

Verfügbare Endpoints

  • POST ?endpoint=send — Eine SMS senden
  • POST ?endpoint=schedule — SMS planen
  • GET ?endpoint=scheduled&client_login=CLIENT_LOGIN&limit=20 — Geplante SMS anzeigen
  • POST ?endpoint=cancel-scheduled — Geplante SMS stornieren
  • POST ?endpoint=bulk — Bulk-SMS-Kampagne erstellen
  • GET ?endpoint=campaigns&client_login=CLIENT_LOGIN&limit=20 — Kampagnen anzeigen
  • POST ?endpoint=cancel-campaign — Kampagne stornieren
  • GET ?endpoint=quota&provider=cryptosms&client_login=CLIENT_LOGIN — SMS-Schätzung für Kunden
  • GET ?endpoint=history&client_login=CLIENT_LOGIN&limit=20 — SMS-Verlauf des Kunden
  • GET ?endpoint=status&id=SMS_ID&client_login=CLIENT_LOGIN — SMS-Status des Kunden

Example: send SMS for your client

curl -sS -X POST "https://magnusbilling.net/sms-api/index.php?endpoint=send" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "client_login": "CLIENT_LOGIN",
    "phone": "+1234567890",
    "message": "Your SMS text",
    "provider": "cryptosms",
    "sender_id": "MyBrand"
  }'

Example: bulk SMS campaign

curl -sS -X POST "https://magnusbilling.net/sms-api/index.php?endpoint=bulk" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "client_login": "CLIENT_LOGIN",
    "phones": ["+1234567890", "+1234567891"],
    "message": "Bulk SMS text",
    "provider": "cryptosms",
    "sender_id": "MyBrand",
    "scheduled_at": "2026-05-10 16:30:00"
  }'
Sender ID / Caller ID wird nicht garantiert. SMS-Kosten werden vom ausgewählten Kundenguthaben abgezogen.

Reseller eSIM API

Reseller können eSIM-Datenpakete mit demselben Reseller X-API-Key verkaufen. eSIM-Käufe werden vom Reseller-Guthaben abgezogen.

Basis-URL https://magnusbilling.net/esim-api/index.php
Autorisierung X-API-Key: YOUR_RESELLER_API_KEY

Verfügbare Endpoints

  • GET ?endpoint=packages&q=Europe&limit=20 — eSIM-Pakete und aktuelle Reseller-Preise anzeigen
  • GET ?endpoint=coverage&package_code=PACKAGE_CODE — Länder und Netze eines Pakets anzeigen
  • GET ?endpoint=balance — Reseller-Guthaben prüfen
  • POST ?endpoint=buy — eSIM-Paket kaufen
  • GET ?endpoint=orders — Reseller-eSIM-Bestellungen, Aktivierungsdaten und Verbrauch
  • GET ?endpoint=sync-order&order_id=ORDER_ID — Aktivierungsdaten und Restdaten aktualisieren

eSIM-Pakete anzeigen

curl -sS \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  "https://magnusbilling.net/esim-api/index.php?endpoint=packages&q=Europe&limit=5"

eSIM-Paket kaufen

curl -sS -X POST "https://magnusbilling.net/esim-api/index.php?endpoint=buy" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -d '{"package_code":"P2CYMUS93"}'

Reseller-eSIM-Bestellungen und Verbrauch

curl -sS \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  "https://magnusbilling.net/esim-api/index.php?endpoint=orders"

Die Bestellantwort enthält Paketname, Preis, Status, ICCID, Aktivierungsdaten, Gesamtvolumen, Verbrauch, Restdaten und Ablaufzeit, sofern verfügbar. Verbrauchsdaten können mit kurzer Netzverzögerung aktualisiert werden.

Security rules

  • The reseller can access only clients created under their Agent account.
  • The reseller can use only their own plans.
  • The reseller cannot access admin clients or other resellers' clients.
  • Der Reseller kann Retail-Guthaben nur eigenen Kunden gutschreiben. Für Anrufe ist weiterhin verfügbares Wholesale-Guthaben des Resellers erforderlich.
  • SIP passwords are returned only once during client creation.
  • Existing SIP passwords and secrets are not returned by client endpoints.
  • White-label portal clients must never see reseller balance, wholesale rates, markup percentage or internal reseller credit logic.
  • Service SIP accounts such as _webN and _ipaN are hidden from normal client SIP lists; Web Phone must use client-softphone-token.

Agent-Portal Konto-API

Zusätzliche Endpoints für White-Label-Agent-Portale: Passwort-Reset, SIP-Passwort-Reset und Kundenprofil-Aktualisierung.

Sicherheitsregeln: Diese Methoden funktionieren nur für Kunden, die dem Reseller gehören. Bestehende Passwörter werden niemals zurückgegeben. Reset-Methoden erzeugen ein neues temporäres Passwort und geben es einmalig an das vertrauenswürdige serverseitige Portal zurück.

Endpoints

curl -sS -X POST "https://magnusbilling.net/reseller-api/index.php?endpoint=reset-client-password" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{"login":"6307210"}'
curl -sS -X POST "https://magnusbilling.net/reseller-api/index.php?endpoint=reset-client-sip-password" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{"login":"6307210"}'
curl -sS -X POST "https://magnusbilling.net/reseller-api/index.php?endpoint=client-profile-update" \
  -H "X-API-Key: YOUR_RESELLER_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{"login":"6307210","email":"client@example.com","phone":"+123456789","language":"en"}'

Service-Konten wie _webN und _ipaN sind vom SIP-Passwort-Reset ausgeschlossen.