Integration Guide
MeridianAuth Quickstart
Integrate cryptographically secured licensing, HWID validation, and anti-tamper barriers into your application in under five minutes.
Step 1: Create an Application
Log in to the MeridianAuth developer console and create a new application instance. You will receive an App ID and an App Secret.
Step 2: Initialize the Client SDK
Before attempting any user authentication or license check, initialize the client object with your application configuration:
Required Parameters
-
app_id: Unique 16-character alphanumeric application identifier.
-
app_secret: Asymmetric salt used for HMAC-SHA256 request signatures.
-
version: Software release version string (e.g. 1.0.0). Used to enforce mandatory client updates.
Step 3: Authenticate License Keys
Invoke the license verification method passing the user's input key. The client runtime automatically hashes local hardware attributes, generates an anti-replay nonce, and verifies the server's signed response before unlocking your application features.
Application Secrets & Security
Your application secret acts as the root of trust between your client binaries and the MeridianAuth validation clusters. Follow these baseline security practices:
Production Best Practices
Never store secrets in plain-text configuration files alongside client binaries. For desktop software, utilize string encryption or compile-time hashing routines to obscure strings against memory dumping.
Hardware ID (HWID) Locking & Resets
When a license key is redeemed for the first time, MeridianAuth permanently binds that key to the calling machine's composite hardware hash.
-
Automated Resets: Configure automatic HWID reset cooldown intervals (e.g., 1 reset permitted every 7 days) via the developer dashboard.
-
Manual Resets: Administrators can instantly clear a bound HWID from the licenses management view.
Error Codes Reference
The verification endpoints return standardized error codes when an authentication check fails:
| Code Identifier |
HTTP Status |
Description |
| ERR_INVALID_LICENSE |
401 Unauthorized |
The license key does not exist, was mistyped, or has been revoked by an administrator. |
| ERR_HWID_MISMATCH |
403 Forbidden |
The license key is already bound to another hardware profile. Requires an HWID reset. |
| ERR_LICENSE_EXPIRED |
403 Forbidden |
The license duration has expired. User must renew access. |
| ERR_TAMPER_DETECTED |
400 Bad Request |
The runtime detected an active debugger, memory hook, or rogue proxy certificate. |
| ERR_VERSION_OUTDATED |
426 Upgrade Required |
The client application version has been deprecated. Mandatory software update required. |
| AUTH_SUCCESS |
200 OK |
License validated. Session token generated and variables unlocked. |
Discord & Webhook Integration
MeridianAuth can dispatch real-time event notifications directly to your Discord server or custom HTTP webhook endpoint:
-
license.redeemed: Fired when a user activates a new key.
-
hwid.reset: Fired whenever an HWID reset is triggered.
-
security.tamper: Critical alert dispatched when a client attempts to bypass memory barriers.