curl --request GET \
--url 'https://api.scanova.io/forms/notification/frequency/' \
--header 'Authorization: YOUR_API_KEY'
[
{ "key": 1, "value": "Per Lead" },
{ "key": 2, "value": "Daily" },
{ "key": 3, "value": "Once a Week" },
{ "key": 4, "value": "Once a Month" }
]
Form Notifications
List form notification frequencies
GET /forms/notification/frequency/
GET
/
forms
/
notification
/
frequency
/
curl --request GET \
--url 'https://api.scanova.io/forms/notification/frequency/' \
--header 'Authorization: YOUR_API_KEY'
[
{ "key": 1, "value": "Per Lead" },
{ "key": 2, "value": "Daily" },
{ "key": 3, "value": "Once a Week" },
{ "key": 4, "value": "Once a Month" }
]
Lists the allowed
Use
frequency values for a form notification.
Requires only account authentication — no
MANAGEMENT_API quota check is applied to this endpoint.curl --request GET \
--url 'https://api.scanova.io/forms/notification/frequency/' \
--header 'Authorization: YOUR_API_KEY'
[
{ "key": 1, "value": "Per Lead" },
{ "key": 2, "value": "Daily" },
{ "key": 3, "value": "Once a Week" },
{ "key": 4, "value": "Once a Month" }
]
key as the frequency value when creating or updating a notification.
Related
- Create a form notification — where
frequencyis set. - Management API overview — the auth scheme and quota architecture 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
Allowed frequency values.
Was this page helpful?