partner
GET /v1/partner/capabilities
What the partner surface supports right now — probe this to open or close a checkout.
Authentication
Send an API key as a bearer token. The key must carry the partner.domains 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 GET https://api.zinndigital.com/v1/partner/capabilities \
-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
Every value is DERIVED from the code that enforces it, never typed: terms and term_discount_bps are the pricing table the cart charges from; refusal_codes is the set a hosting order can be refused with (the raise path refuses any other), and refuses_unfulfillable / region say whether plan_not_fulfillable / the region refusals are among them; plans lists every site-hosting plan with orderable and regions from the SAME functions createPartnerHostingOrder refuses on — so a plan or region published here is accepted there, and one that is not is refused. version changes when the hosting-order contract does. Requires partner.domains.
Response
| Name | Type | Required | What it is |
|---|---|---|---|
site_moves | object | No | The site-move contract (createPartnerSiteMove). Every value is derived: served from the mounted route, plans from the same functions a move is refused on. |
hosting_orders | object | Yes | — |
Errors this endpoint can return
401 · 403 · 429