API Reference v3.0
Welcome to the RDX Authentication API documentation. This reference provides detailed information on all available endpoints, security mechanisms, and integration guides for advanced developers who wish to build custom implementations.
Base URL: https://rdxcommunity.qzz.io
Connection Guide
How to correctly use the Base URL in your applications.
code RDX Native API
For direct HTTP requests from Python, Node.js, or cURL.
Example: /rdx/api/variables
javascript KeyAuth SDKs
For C#, C++, and Java SDKs using the compatibility bridge.
Use this in the Host or API URL field.
Important: Do NOT append :5000 to the URL. Since you are using a domain, standard HTTPS (port 443) is used automatically.
Security & HMAC
Preventing man-in-the-middle and replay attacks.
RDX uses HMAC-SHA256 signatures for all critical requests. This ensures that the data sent by the client cannot be tampered with during transit.
Signature Generation
Combine the payload fields with your App Secret in a specific order:
signature = HMAC_SHA256(license_key + hwid + owner_id + timestamp, app_secret)
Rate Limiting
Protecting infrastructure from abuse.
Global Limit
100 / 15m
Standard browsing and non-critical calls.
Auth & SDK Limit
20 / 15m
Strict limit for login and SDK validation routes.
Exceeding these limits will result in a 429 Too Many Requests response. Ensure your SDK handles retries gracefully.
Core Endpoints
The pulse of the RDX ecosystem.
/rdx/api/auth/login
Authenticates a user via traditional username and password credentials.
Request Body
{
"username": "user123",
"password": "securepassword"
}/rdx/api/license/validate
Validates a license key against the hardware ID of the device. Requires HMAC signature.
Request Body
{
"license_key": "RDX-XXXX-XXXX",
"hwid": "device_unique_id",
"app_name": "Pro_Tools",
"owner_id": "owner_id_from_dashboard",
"timestamp": 1700000000,
"signature": "hmac_signature_hex"
}/rdx/api/hwid-reset/request
Allows users to request a hardware reset from the administrator. Requires a Bearer Token.
Request Body
{
"app_id": "1",
"reason": "Upgraded my PC"
}/rdx/api/variables
Fetch dynamic variables, offsets, or settings for your application.
Query Parameters
Example Response
{
"success": true,
"variables": {
"offset_x": "0x123",
"version": "1.0.5"
}
}Discord Integration Guide
Automate your community management and sync RDX with your Discord Server.
Official Developer Portal
Start by visiting the Discord Developer Portal to create your application.
Create a New Application
Click on the "New Application" button at the top right. Give it a name (e.g., "RDX Auth Bot") and agree to the Terms of Service.
Configure Your Bot
Navigate to the "Bot" tab in the left sidebar. Click "Reset Token"
to generate your unique Bot Token.
Security Tip:
Never share this token. RDX uses it to communicate with Discord's API.
Enable Privileged Gateway Intents
Scroll down in the "Bot" tab to the "Privileged Gateway Intents" section. Enable "Server Members Intent" and "Message Content Intent". This is required for RDX to verify user roles and respond to commands.
Get Client ID & Secret
Go to the "OAuth2" tab. Here you will find your Client ID and Client Secret. Enter these into the RDX Dashboard settings to finalize the link between your software and your Discord server.