GET /v1/seo-connection/notices

Authentication

Send an API key as a bearer token. The endpoint checks billing.view; a key without it is refused with 403, not 404.

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/seo-connection/notices \
  -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

What the Zinn® SEO plugin shows in wp-admin and may send from the site's own mailer: low balance, the 30-day run-out forecast, scheduled checks paused for credit, their resume, ranks that fell, backlinks lost, pages dropped from Google, AI answers that stopped or started quoting the site, new brand mentions, and every SEO Guard problem and its fix. Organization-wide notices (credits) and this site's own domain only, newest first, the last 90 days. Needs the seo.notices scope. Each item is rendered from the SAME template as the Zinn Digital® e-mail, in locale (a WordPress locale such as de_DE or a registry code; unknown falls back to English): title and message for the notice, site_email for the site's own mailer, with default_on saying whether the plugin sends it unless the site owner switched it off. Send If-None-Match with the last ETag; an unchanged feed answers 304 with no body. Cache for 15 minutes.

Parameters

Response

Errors this endpoint can return

401 · 403