Builder docs
Test your AppGild license-check integration before you submit your app. Two independent checks: (1) confirm AppGild sees a given key as active for your slug, (2) confirm your app's sign-in gate actually unlocks when given that key.
New here? Read the full integration guide + FAQ first.
We'll hit the live /api/license/verify endpoint with the exact same request your app will send. Use a key that should be active (your own test purchase, or a buyer's key if you're already live).
/app/ in your AppGild listing URL. Example:scopeforge.Paste the URL of your deployed app. We'll load it in a frame below so you can paste the same key into your gate and see if it unlocks. (This proves your gate code is wired correctly — the snippet's fetch call works, the JSON parsing works, and your unlock logic fires.)
Doesn't load? Some hosts (and most production setups) block embedding in iframes via X-Frame-Options or Content-Security-Policy headers — that's normal and secure. If you see a blank frame, just open your app URL in a new tab manually and test the gate there.
Check 1 returns active, Check 2 unlocks your app. 🎉 You're done. Submit your app.
Check 1 returns active, Check 2 stays gated. Your APP_SLUG in the snippet doesn't match what AppGild has. Re-check the slug in your gate code matches your listing URL exactly.
Check 1 returns no_active_purchase, you swear the key is valid. Two likely causes: (a) the key has a typo (regenerate the buyer's key on their /purchases page if needed), or (b) the slug in your gate code doesn't match this app's listing slug.
Check 1 returns active, Check 2 throws a CORS error in browser console. Your gate code probably has credentials: 'include' in the fetch call — remove that. The reference snippet doesn't include it.