curl --request GET \
--url 'https://api.scanova.io/tracking/notification/frequency/' \
--header 'Authorization: YOUR_API_KEY'
["daily", "weekly", "monthly"]
Tracking
List notification frequencies
GET /tracking/notification/frequency/
GET
/
tracking
/
notification
/
frequency
/
curl --request GET \
--url 'https://api.scanova.io/tracking/notification/frequency/' \
--header 'Authorization: YOUR_API_KEY'
["daily", "weekly", "monthly"]
Lists the valid frequency values for scheduled email report notifications (e.g. QR Code analytics report subscriptions) — the same list backing the
The response is a flat array of strings, not paginated — use it to populate a frequency selector rather than hardcoding the list.
Preference model’s FREQUENCIES field.
Requires a Management API key. This is a static-ish reference lookup with no per-account data — just the account authentication, no additional quota or permission gate.
curl --request GET \
--url 'https://api.scanova.io/tracking/notification/frequency/' \
--header 'Authorization: YOUR_API_KEY'
["daily", "weekly", "monthly"]
400 on an unexpected server-side error building the list (rare — this endpoint has no user input to reject).
Related
- Management API overview — the auth scheme this endpoint is part of.
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
Valid frequency values.
Was this page helpful?