Endpoint
Status Values
| Status | Meaning |
|---|---|
queued | The generation record exists but work has not started yet |
generating | Tented is actively generating the HTML |
completed | Generation finished successfully |
failed | Generation failed |
Request Example
Response Examples
In-Progress Response
Completed Response
When generation succeeds, the response includes aresult object:
Failed Response
If generation fails, the response includes anerror field:
Publication Object
If the original create request usedauto_publish: true, the status response also includes a publication object.
| Field | Type | Notes |
|---|---|---|
status | pending | published | published_with_warnings | failed | Publication lifecycle state |
published_url | string | Present when the tent was published |
requested_custom_page_alias | string | The alias you asked for |
applied_custom_page_alias | string | null | The alias that was actually applied. null means publish fell back or failed |
warnings | array | Returned when publish succeeded with warnings |
error | object | Returned when publish failed |
Published Response
Published With Warning Response
If the requested alias is already taken, Tented still publishes the tent at its default path and returns a warning:Publication Failure Response
If generation succeeds but auto-publish fails, the generation status still remainscompleted and the failure is reported under publication:
Root Page Publishing Response
If you requested/ as the alias, the status response returns /:
Common Errors
| Status | Cause |
|---|---|
400 Bad Request | tentId is missing or not a valid UUID |
401 Unauthorized | Missing or invalid bearer token |
404 Not Found | The tent does not exist in the workspace associated with your API key |
Back to API Overview
Review the full Vibe Coding API workflow and endpoint map.