hosting
POST /v1/sites/{siteId}/cms-target/test
Check the credential actually works, against the real CMS.
Authentication
Send an API key as a bearer token. The key must carry the links.edit permission; 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 POST https://api.zinndigital.com/v1/sites/{siteId}/cms-target/test \
-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
Contacts the site's CMS with the stored credential and records what happened. Gated on links.edit. ⭐ This is what promotes a target from "configured" to "ready". A preset we shipped from a vendor's documentation is a claim; a probe against the customer's own instance is a measurement, and nothing in the picker reads green until this has answered. ⛔ A failure here is a 200 carrying reachable: false and a reason, not an error status. "We could not reach it" is the answer to the question that was asked.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | string | Yes | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
site_id | string | Yes | — |
reachable | boolean | Yes | — |
identity | string | Yes | — |
code | string | Yes | — |
detail | string | Yes | — |
suitability | string<ready, needs_setup, unknown, unsuitable, blocked> | Yes | — |
Errors this endpoint can return
401 · 403 · 404