POST /v1/seo-connect/token

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 POST https://api.zinndigital.com/v1/seo-connect/token \
  -H "Content-Type: application/json" \
  -d '{ "device_code": <string> }'

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

The plugin polls this every interval seconds (RFC 8628 §3.4). Until the request is approved it answers 400 with error.code authorization_pending; polling faster is slow_down; a refused request is access_denied; an unknown, expired or already used code is expired_token. Once approved it answers 200 with the zsc_ token — exactly once (Cache-Control: no-store); the engine stores only its SHA-256. A site that connects again to the same organization retires its previous token.

Request body

Response

Errors this endpoint can return

400 · 422 · 429