List artifact templates

The templates an artifact can start from: the built-in ones and those saved in the workspace, each with its id, kind, name, description and body (Markdown, or a JSON spec).

GET/workspaces/{workspace}/artifact-templates

Narrow with kind.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: artifact with action templates, and the same inputs
Scope: An access token needs artifacts:read.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s slug, e.g. “acme”.

Query parameters

Name	Type	Required	Description
`kind`	string	No	doc, slides, design or dashboard. One of `doc`, `slides`, `design`, `dashboard`.

Example request

curl "https://api.g1t.sh/workspaces/acme/artifact-templates?kind=doc" \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

[
  {
    "id": "builtin:doc:meeting-notes",
    "kind": "doc",
    "name": "Meeting notes",
    "description": "Who came, what was decided, and what happens next.",
    "icon": "📝",
    "builtin": true,
    "body": "# Meeting notes\n\n## Attendees\n\n## Decisions\n\n## Next steps\n"
  }
]

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository.
404	`not_found`	It does not exist, or you cannot see it.
422	`invalid`	The input is not valid. `message` says which field and why.