How to Migrate from KeyAuth to AuthCord in Under 15 Minutes
KeyAuth handles licensing. AuthCord handles the entire ecosystem: licensing, payments, storefronts, Discord integration, community forums, and more. Here's how to switch without losing any of your existing users.
Why developers switch
KeyAuth is a licensing tool. It validates keys and binds HWIDs. But it doesn't sell your product, manage your Discord server, host your community, or give your customers a dashboard. You end up stitching together 4-5 different services.
AuthCord replaces all of them with one platform:
- +Web storefronts with Stripe, PayPal, and crypto checkout
- +Discord bot with role sync, slash commands, and verification
- +HWID binding with multi-device slots and cooldowns
- +Built-in community forums with moderation
- +Webhooks, analytics, file distribution, offline tokens
- +Reseller system with branded storefronts and territory locking
What gets migrated
The migration process
1. Export your data from KeyAuth
Use the KeyAuth Seller API to pull your users and subscriptions. You need your Seller Key from Account Settings.
# Fetch all users
GET https://keyauth.win/api/seller/?sellerkey=KEY&type=fetchallusers&format=json
# Fetch all subscriptions (via user data)
GET https://keyauth.win/api/seller/?sellerkey=KEY&type=userdata&user=USERNAME
2. Create your AuthCord app
Sign up (free), create an app, and connect your Discord server. You don't need to create products manually. The importer auto-detects your KeyAuth subscription levels and creates matching products for you.
3. Run the importer
In your app dashboard, click the Migrate tab, select KeyAuth, and paste your JSON. The importer shows a preview before making any changes:
- - How many users will be created
- - Which products will be auto-created
- - How many HWIDs will be bound
- - Which users are banned
- - Any warnings or issues to review
Confirm, and it processes everything in seconds. Discord roles sync automatically.
4. Update your application
Replace your KeyAuth API calls with AuthCord's validation endpoint:
POST https://keyauth.win/api/1.2/ (type=login)
POST https://authcord.dev/api/v1/auth/validate
Header: X-API-Key: dax_your_key
Body: { "discordId": "...", "hwid": "...", "product": "Pro" }
We also have a Python SDK if you prefer a library over raw HTTP calls.
API comparison cheat sheet
| Action | KeyAuth | AuthCord |
|---|---|---|
| Validate user | type=login | POST /api/v1/auth/validate |
| Check subscription | type=checkblack | Included in validate response |
| Get user variables | type=getvar | Entitlements + remote config |
| Download file | type=file | GET /api/v1/files/:id/download |
| Reset HWID | Seller API only | Dashboard, API, or bot /hwid-reset |