curl "https://api.scanova.io/campaign/active/user-log/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
{
"id": 118,
"is_popup_disabled": false
}
Campaign
Get your dismissal state for the active campaign
GET /campaign/active/user-log/
GET
/
campaign
/
active
/
user-log
/
curl "https://api.scanova.io/campaign/active/user-log/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
{
"id": 118,
"is_popup_disabled": false
}
Returns the authenticated account’s log row for the currently active G2 review campaign on the Management API host (
Pair this with Get the active review campaign to decide whether to show the prompt: if there’s an active campaign and either this call 404s or
api.scanova.io), authenticated with your raw Management API key.
GET https://api.scanova.io/campaign/active/user-log/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
is_popup_disabled is false, show it; otherwise don’t.
curl "https://api.scanova.io/campaign/active/user-log/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
{
"id": 118,
"is_popup_disabled": false
}
Why this 404s so often
This endpoint 404s in two different situations, and both mean the same thing to a caller — “show the popup”:- There’s no campaign currently active at all (same condition
GET /campaign/active/404s under). - There is an active campaign, but this account hasn’t logged any interaction with it yet — the log row is created lazily, on the first
POST /campaign/user-log/call, not automatically when the campaign starts.
Related
- Get the active review campaign — the campaign this log row applies to.
- Log that the review popup was shown, dismissed, or submitted — create the row this endpoint reads.
- Update your campaign log — update the row this endpoint reads.
- 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
The account's log row for the active campaign.
Was this page helpful?