LibreAuth

Seller API

Programmatic management for applications, keys, users, and file hashes — built for Discord bots and automation.

Query-string Seller API

Pass sellerkey, type, and parameters via GET or POST — built for Discord bots and automation scripts.

Endpoint

https://libreauth.nutexe.dev/seller-api/

Supports GET (query string) and POST (application/x-www-form-urlencoded or JSON body). Discord bots on Node.js usually call GET with fetch().

Authentication

sellerkeyPer-app API key from Panel → select application → Seller API
typeAction name — addhash, addkey, fetchusers, etc.
WARN
Never expose sellerkey in client apps or public repos. Store it in bot environment variables only.
INFO
Each application allows one Seller API key. Delete the existing key before creating a new one.
INFO
Seller API requires Pro or Enterprise plan (seller_api feature). Free and Developer tiers are blocked. See Billing Plans.
INFO
Protocol v2: Seller API already manages apps whose clients use /api/v2/. The Seller wire stays sellerkey JSON (not HMAC). Client Protocol v2 needs Enterprise (api_v2); Seller API itself needs Pro+. type=info returns capabilities.api_v2. fetchsessions includes bound_hwid, last_req_at, has_device_key for v2 device sessions.

Key Permissions & IP Whitelist

Each seller key can restrict operations (apps, keys, users, …) and optional IP whitelist. If your bot runs on a VPS, add the server IP in Panel → Seller API → key settings.

Quick Test

Verify key
curl -G 'https://libreauth.nutexe.dev/seller-api/' \
  --data-urlencode 'sellerkey=YOUR_SELLER_KEY' \
  --data-urlencode 'type=info'

Discord Bot

Official open-source bot — production-ready with Docker:

libreauth-Bot

GitHub — /getkey, /addhash, /extend-user, multi-app, Docker.

Integration Guide

Setup, command map, env vars, DIY fetch example.

Add Application Hash

Whitelist MD5 after each build — stops E04/E05 on clients.
INFO
Full reference: All Seller Endpoints · Anti-Tamper / Hash Check · Seller API logging