GET /v1/connector/status

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/connector/status

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

Unauthenticated by session, authorised by the per-site bearer token minted when the customer connected. The caller is PHP on a server we have never seen. ⛔ Unlike /v1/connector/backup/claim, this endpoint DOES distinguish a good token from a bad one, and that is not a regression of that decision — it is a different question. It says nothing about a site: it says whether the token the caller already holds is live, which is exactly what the legitimate holder needs and is worth nothing to anybody else. Learning one bit about somebody else's site would require possessing their token first. ⛔ A refused account and an outage are different answers with different remedies, so a refusal carries refused: true and a reason written for the site owner (CLAUDE.md §2.57). The plugin shows the reason and links to billing; it never reports a suspension as an outage or an outage as a suspension.

Response

Errors this endpoint can return

429