surveys

GET /v1/surveys/active

The surveys this organisation may currently be shown.

All surveys endpoints

Authentication

Send an API key as a bearer token. The key must carry the org.read permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/surveys/active \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Every decision ABOUT the customer is applied here, server-side, before a survey crosses the wire — good standing, the per-organisation kill switch, and archived or stopped surveys. The client is left with exactly the three things only it can know: which route it is on, whether this person has seen a survey recently, and the sampling die roll. ⛔ `available` is a first-class part of the answer. A survey store that is unconfigured, rate-limited or unreachable is NOT the same fact as "you have no surveys", and `surveys: []` on its own would tell the app every survey had been archived. On `available: false` the client keeps its previous answer. Requires `org.read`.

Parameters

NameTypeRequiredWhat it is
org_id (query)stringNo
distinct_id (query)stringNoThe browser's analytics distinct id, so the join resolves.

Response

NameTypeRequiredWhat it is
availablebooleanYes
reasonstring<, unconfigured, unreachable, refused, not_found, malformed>Yes
surveysSurvey[]Yes

Errors this endpoint can return

401 · 403