Templates
Publish template
Publish a template document to your registry.
POST
Publish template
Publishes a template to your registry. The request body is a complete
orgo.ai/v1 document, sent as YAML (Content-Type: application/yaml) or JSON (Content-Type: application/json).
Publishing templates requires a Scale plan. Every account can still launch curated templates and any template you’ve published.
Refs are immutable. Once
namespace/name@version is published, re-publishing the same ref with different content returns 409. Bump template.version to ship a change, or pass ?force=true to overwrite the version in place while iterating.Query parameters
Build the golden snapshot immediately after publishing. Equivalent to calling Build template yourself.
Overwrite an existing version in place (delete + republish). Useful for fast iteration on a single version number.
Request body
The raw template document. Validate it first with Validate template to catch errors without writing anything.Response
The published ref,
namespace/name@version.Content-addressed SHA-256 digest of the canonical template.
ISO 8601 publish timestamp.
Present only when
?auto_build=true. The status of the build that was kicked off, e.g. "building".Example
Response
Errors
| Status | Meaning |
|---|---|
400 | Empty body, or unparseable YAML / JSON. |
401 | Missing or invalid API key. |
403 | Publishing requires a Scale plan or higher. |
409 | A different template is already published at this namespace/name@version. Bump the version or use ?force=true. |
422 | The template failed validation. The errors array lists each problem with its field, code, and message. |
Authorizations
API key authentication. Get your key at orgo.ai/workspaces
Query Parameters
Build the golden snapshot immediately after publishing.
Overwrite an existing version in place (delete + republish). Useful while iterating on one version number.
Body
The orgo.ai/v1 template document as YAML.
Publish template