The Hoody exec service can scaffold ready-to-run script code from templates. This is deterministic template rendering, not AI or LLM-based generation: you choose a template, supply its inputs, and the service returns fully-formed, executable source code.

Templates come in two flavors. Built-in templates ship with the platform for common scripting patterns and languages. Custom templates are ones you create, version, and maintain yourself for your own repeatable use cases.

Available operations

The template system supports six operations, all documented in full on the Script Templates page:

• List templates — GET /api/v1/exec/templates/list
• Preview a template — GET /api/v1/exec/templates/preview
• Generate code from a template — POST /api/v1/exec/templates/generate
• Create a custom template — POST /api/v1/exec/templates/create-custom
• Update a custom template — PUT /api/v1/exec/templates/update-custom/:name
• Delete a custom template — DELETE /api/v1/exec/templates/delete-custom/:name

Authentication

All requests authenticate with the standard API key header:

Authorization: Bearer <HOODY_API_KEY>

Note

No workspace scoping, generation quota, or rate-limit headers are applied to template requests. Templates are available to every authenticated API key.

Typical workflow

1. Call List templates to discover which built-in and custom templates are available.
2. Call Preview with a template name to inspect its expected inputs and output shape without generating.
3. Call Generate with the required inputs to produce the final script source.
4. For organization-specific patterns, call Create custom template and manage it with the Update and Delete operations.

Next steps

• See the full Script Templates reference for request schemas, parameters, and response examples for each operation.
• After generating a script, validate it with the Code Validation API before deploying or executing it.