Add-ons: extra content your customers unlock with an add-on key
An add-on is extra content the customer unlocks inside your program, while signed in with their own licence key or account: a map pack, a skin set, a Pro mode. You sell it with add-on keys. The customer types the key in a box you show and the add-on is theirs at once, with no second sign-in. An add-on key never signs in by itself
- In App settings → Add-ons, add one with a name, a code your program checks (like
night_city) and how long its keys give it: for good or a number of days - Make keys makes its keys in your app's key format. Its keys shows each key: unused, or who added it and when
- Your program calls
redeemAddon(key). Sign-in and every heartbeat bringaddons: the add-ons the customer has, each with its code and when it ends - In Files, set Who gets it of a protected file to an add-on. Only customers who have it can fetch it, so a cracked program that flips the check still has nothing to load
- A second key of the same add-on adds its days on top. Switch an add-on off and its keys are refused, while customers who have it keep it
- Give or take an add-on by hand from the side panel of a key in Licences or of an account in Users
- Customers see their add-ons on the customer page and can add a key there too
- The webhook event
addon.redeemedtells your server when a customer adds a key
SDKs: PWFAuth 1.8.0 on NuGet (RedeemAddonAsync, Addons, HasAddon, AddonsChanged) and pwfauth 1.6.0 on PyPI (redeem_addon, addons, has_addon, on_addons_changed). Both fetch protected files too. The SDK generator has redeemAddon and getAddons for all 11 languages