A User in Qonversion represents a single app user across platforms. Each user has a unique Qonversion User ID (prefixed withDocumentation Index
Fetch the complete documentation index at: https://documentation.qonversion.io/llms.txt
Use this file to discover all available pages before exploring further.
QON_) that is automatically generated by the SDK on first launch. Most user-scoped operations live under /v4/users/{user_id}/….
Key concepts
- Qonversion User ID — Auto-generated identifier (e.g.,
QON_3af4c5b8a4d24f21b72e9d0c8aef9d4e). The server emits a UUID with dashes stripped, so the suffix is always 32 lowercase hex characters. - Environment — Each user belongs to either
prod(production) orsandboxenvironment. - Identity — Users can optionally be linked to your own user ID system via the Identity API.
- Sub-resources — Properties, purchases, and entitlements live under dedicated endpoints, documented in User Properties, Purchases, and Entitlements.
Available endpoints
| Method | Endpoint | Description | Status |
|---|---|---|---|
| POST | /users | Create a user (server generates the QON_… id) | New |
| GET | /users/{user_id} | Get a user | Updated — v3 |
POST /v3/users/{id} accepted a client-supplied id. v4 standardises on server-issued ids across every resource — pass only the environment in the body, and use the returned id / Location for follow-up calls. Pair with an Idempotency-Key header to make retries safe.