Skip to main content
Support Online
MirrorLooking Glass
RabisuRabisu
Client Panel
TutorialsKnowledgebaseReseller APIReseller Module

Rabisu Reseller API — Overview

The Rabisu Reseller API is a REST API that lets resellers sell Rabisu Virtualizor VPS products through their own WHMCS installation. It provides order creation, service lifecycle management (suspend, terminate, rebuild), resource upgrades, credit balance queries, and webhook notifications.

Complete documentation in one file (for AI)

Instead of browsing page by page, you can download the entire API documentation (guides, every endpoint, parameters, responses, examples and data schemas) as a single text file. Upload it to an AI assistant such as ChatGPT or Claude and ask your integration questions directly.

📄 Download the English documentation (.txt) · Türkçe sürüm (.txt)

Basics​

PropertyValue
Production base URLhttps://api.rabisu.com/api/v1
ProtocolHTTPS required (TLS)
AuthenticationHTTP Basic Auth (API Key + Secret)
Content typeapplication/json
VersionAll paths under /api/v1

Request Format​

All request bodies must be JSON. Authentication is sent on every request using the HTTP Basic Auth header (see Authentication).

curl -u "rsk_live_xxx:rsks_yyy" \
  https://api.rabisu.com/api/v1/auth/me

Standard Response Envelope​

Every response uses the same envelope. Success:

{
  "success": true,
  "data": {
    "reseller_id": 42,
    "name": "Example Reseller"
  },
  "meta": {
    "trace_id": "1f9a...uuid",
    "timestamp": "2026-07-22T12:00:00Z"
  }
}

Error:

{
  "success": false,
  "error": {
    "code": "insufficient_credit",
    "message": "Credit balance is insufficient.",
    "details": { "required": "10.00", "available": "3.50" }
  },
  "meta": {
    "trace_id": "1f9a...uuid",
    "timestamp": "2026-07-22T12:00:00Z"
  }
}
  • success: Result of the operation (true / false).
  • data: Present only in successful responses.
  • error: Present only in error responses — code (English slug), message (human-readable), and optional details.
  • meta.trace_id: Unique trace identifier per request. Include it when contacting support.
  • meta.timestamp: ISO 8601 UTC timestamp.

Trace ID​

Every response returns an X-Request-ID header and a meta.trace_id field. If you send your own X-Request-ID header, the system preserves it; otherwise a UUID is generated automatically. Keep this identifier in your logs for troubleshooting.

Next Steps​