curl "https://api.scanova.io/user-logs/user-activity/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
{
"qr_static_created": true,
"qr_dynamic_created": true,
"feature_password_protection": false,
"lead_list_created": false,
"onboarding_1_continue_clicked": true,
"qr_first_created": "2026-06-01T10:00:00Z",
"total_qr_codes": 24,
"total_shared_users": 3
}
User Logs & Activity
Retrieve activity milestone flags
GET /user-logs/user-activity/
GET
/
user-logs
/
user-activity
/
curl "https://api.scanova.io/user-logs/user-activity/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
{
"qr_static_created": true,
"qr_dynamic_created": true,
"feature_password_protection": false,
"lead_list_created": false,
"onboarding_1_continue_clicked": true,
"qr_first_created": "2026-06-01T10:00:00Z",
"total_qr_codes": 24,
"total_shared_users": 3
}
Retrieves the account’s current feature-usage milestone flags, on the Management API host (
Around 50 boolean fields track whether the account has ever performed a given action (e.g.
api.scanova.io), authenticated with your raw Management API key.
GET https://api.scanova.io/user-logs/user-activity/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
curl "https://api.scanova.io/user-logs/user-activity/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
{
"qr_static_created": true,
"qr_dynamic_created": true,
"feature_password_protection": false,
"lead_list_created": false,
"onboarding_1_continue_clicked": true,
"qr_first_created": "2026-06-01T10:00:00Z",
"total_qr_codes": 24,
"total_shared_users": 3
}
qr_static_created, feature_password_protection, lead_list_created) — once true, a flag never reverts to false. A handful of fields are computed rather than boolean, such as qr_first_created and total_qr_codes.
Related
- Set an activity milestone flag — flip a flag to
true. - Management API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Response
200 - application/json
The account's activity flags.
Was this page helpful?