Glossary
Terms used across all platform docs.
| Term | What it is | Who creates it | When you use it |
|---|---|---|---|
| API key | Secret identifying your app | Azeoo team (contact) | initialize(apiKey) |
| SDK Secret Key | HMAC key for signing User JWTs | Azeoo team (provided with API key) | Your backend — Creating the User JWT |
| SDK token | Short-lived token for SDK backend calls | SDK (after successful initialize) | Internal; you rarely touch it |
| User JWT | Token identifying the logged-in user, signed by your backend with the SDK Secret Key | Your backend — see Creating the User JWT | connect / connectUser |
| Profile id | Azeoo user id string | Returned by connect | Store if your app needs to reference the user |
| Connector | Optional link to resamania2 / deciplus | Configured on API key in Client Platform | initialize options when key has connectors |
initialize vs connect
| initialize | connect | |
|---|---|---|
| Purpose | Start SDK engine, exchange API key | Attach logged-in user |
| User | None | Required (JWT + profile) |
| Call when | App start (or after dispose) | After your login flow |
| Call again when | API key or global config changes | User switches account |
Common mistakes
| Mistake | Fix |
|---|---|
Passing userId into connect | Pass only JWT + gender + height + weight; id goes inside the JWT payload |
| Using test JWT in production | Use your backend-issued JWT signed with the SDK Secret Key |
Showing SDK UI before connect | Wait for connect success |
Calling initialize on every screen | Once per process (unless you dispose) |
| Confusing API Key with Secret Key | API Key goes in initialize(); Secret Key is used by your backend to sign JWTs |