AppKeys and management keys
Which key belongs in your app?
MyApp needs an AppKey so AuthlyX knows which application is connecting. That key can be included in distributed customer software. It identifies the app; it does not give everyone permission to manage the developer account.
An Elite Key or Bot Key is different. Those credentials authorize management operations according to their permissions. Keep them on a server or in the authorized bot service, never in a desktop binary, browser bundle or public repository.
An AppKey is not an unbreakable app secret
Someone who can inspect the customer’s software can read embedded values. AppKeys therefore cannot prove that an HTTP request came from an unmodified program. AuthlyX uses authenticated identities, installation proof and server-side authorization to decide access.
Use the AppKey and version from the same application as your test license. Initialize first, then log in. Never paste a management key into the AppKey field to fix a failed login.
Rotating credentials
Rotate management keys when a server or bot credential may have leaked. Give each integration a descriptive name, only the permissions it needs and an expiry when appropriate. Revoke old keys after updating the service.
AppKey rotation also needs a release plan: existing software may still contain the previous key. Test the transition before changing a live app. Verification public keys are a third category: they let the SDK verify server signatures and do not grant management access. Keep trusted verification keys in step with the API’s signing-key rotation.
Check your release
Search the compiled frontend configuration and repository for management credentials. Confirm that customer software can authenticate but cannot create arbitrary licenses or inspect another account. The warning in API Reference applies to both Elite Keys and Bot Keys.

