ai

GET /v1/ai/site-builds/{siteBuildId}

One AI-built site, with every generated file.

All ai endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the sites.view 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/ai/site-builds/{siteBuildId} \
  -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

The draft and its complete files map. A build belonging to another organization is a 404 rather than a 403, because a 403 would confirm the identifier exists. Requires sites.view.

Parameters

NameTypeRequiredWhat it is
siteBuildId (path)UuidYes—

Response

NameTypeRequiredWhat it is
buildSiteBuildYesOne "describe a site and we build it" run. files is present on the detail and create responses and absent from the list, deliberately: a generated tree can be a hundred…
trialSiteBuilderTrialNoThe one-time free allowance for the AI site builder. One grant per organization, for ever — not monthly, and not per site. granted is true because the credit was actually…

Errors this endpoint can return

401 · 403 · 404 · 429