zinn-campaigns

GET /v1/store-connect/campaigns

The Zinn® Campaigns WordPress plugin reads whether its Pro add-on is unlocked.

All zinn-campaigns endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

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/store-connect/campaigns

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

Store token only (Authorization: Bearer zou_…). The ENGINE decides Pro, never the plugin (docs/1052 §11.9b). active = the org is in good standing and holds a live, active, non-zero-priced plan on the Zinn® Campaigns line (any paid plan, no separate licence). trial = no paid plan, the org is active and fewer than 30 days have passed since the org first connected a store (disconnecting and reconnecting never restarts it). lapsed = anything else: the add-on keeps every setting and stops its Pro features until a paid plan is live again.

Response

NameTypeRequiredWhat it is
prostring<active, trial, lapsed>Yes—
plan_paidbooleanYesA paid Campaigns plan exists (it may be unusable while the account is not in good standing).
plan_codestringYesThe paid plan's code, or empty.
trial_daysinteger<30>Yes—
trial_ends_atobjectYes—

Errors this endpoint can return

401 · 429