Skip to content

Get a template

GET /template/{id}

Returns one template with its full entry list (a template never carries a `connection_id`), and `access_summary` when the caller may see who it is shared with. Only the owner or someone with a grant can open a template; anyone else gets `404`, never `403`, including a holder of `template:manage`.

Path Parameters

idstring
required·

Template id (tpl_…).

Response Body

access_levelstring

The caller's access: owner, or a granted view/use/edit level. An org owner or admin sees a template only when they own it or it has been shared with them, like any other member.

access_summaryobject

Present on a GET /template row exactly when that row's can_see_shares is true — the caller owns it, holds edit, or administers a team it is granted to. Same gate and same reasoning as the toolbox row's.

org_levelstring,null

Level of the org-wide grant, or null when there is none.

Possible values:
viewuseeditnull
previewobject[]

At most 5 grantees, broadest first (org, then teams, then members), for a hover preview.

4 properties
grantee_idstring,null
grantee_typestring
Possible values:
userteamorg
levelstring
Possible values:
viewuseedit
namestring,null

Display name; null for org grants and for grantees no longer in the org.

team_countinteger
totalinteger

Every grant, the org-wide one included.

user_countinteger
access_viastring

How the caller reaches this template, not who else can. owner: they own it. direct: a grant names them personally. team: a grant to a team they belong to (or administer), named in access_via_team. org: an organization-wide grant. When several sources apply, the broadest wins and the access level plays no part: owner, else org, else team, else direct. A caller with edit personally and view org-wide reads org, because this field says how far the template reaches, not what the caller may do with it. It describes only the caller's own access, so a view or use grantee still gets it while the list of other grantees stays hidden. Absent when nothing reaches the caller (for example, the former owner after a transfer of a resource that was never shared); absent never means org.

Possible values:
ownerdirectteamorg
access_via_teamobject

Present exactly when access_via is team, absent otherwise. The team the caller reaches this template through — one of their own teams, never a disclosure about anybody else.

idstring

Team id (team_…).

namestring,null

Team display name, or null when the team no longer resolves in the directory — the same null contract every resolved grantee name carries.

can_draft_skillboolean

Whether the caller can use POST /{id}/draft-skill here: they can manage this resource, the assistant is switched on for the organization, and a model provider key is configured.

can_manageboolean

Whether the caller may edit this template's own settings — owner, or edit access. No template:manage fallback. Mirrors PATCH /template/{id}.

can_revoke_shareboolean

Whether the caller may grant or revoke access to this template. It matches can_share and is separate from can_manage: an edit grantee whose role omits template:share can edit the template but cannot change who else has access. Mirrors DELETE /template/{id}/share/{aclId}.

can_shareboolean

Whether the caller may share this template — owner, edit access, or template:share. No template:manage fallback. Mirrors POST /template/{id}/share's own check.

can_stampboolean

May the caller create a toolbox from it (POST /toolbox { template_id }): can_use, and member:manage when an entry binds a member field or caller.external_id. False with can_use true: the stamp is refused 403 caller_binding_forbidden. On list rows, detail and both writes.

can_transferboolean

Whether the caller may transfer or delete this template — ownership, full stop. No template:manage fallback. Mirrors POST /template/{id}/transfer and DELETE /template/{id}.

can_useboolean

Whether the caller may stamp a toolbox from this template — based on the caller's ownership or grant level. Present on every list and detail row for both templates and toolboxes.

connectorsobject

Which integrations this template's tools come from, summarized as at most a handful of connectors (the same shape as on a toolbox row). Present on every GET /template row and on every command response (POST /template, GET /template/{id}, PATCH /template/{id}, POST /template/{id}/transfer). total: 0 means no connector-backed tools (empty, or synthetic-only), never "not computed".

previewobject[]

At most 5 connectors, ordered by entry count descending then slug ascending, so the dominant integration leads and the order is stable across requests. Each entry arrives resolved: there is no follow-up GET /connector/{slug} to make.

3 properties
logostring,null

The connector's square icon when it has one, else its wordmark logo, else null (the connector carries neither picture, or could not be resolved). Draw it in a square tile; render initials from name when it is null.

namestring

Catalog label. Falls back to the slug when the connector no longer resolves (deleted from the catalog), so a row always has something to draw.

slugstring

Connector slug — connectors are keyed by slug, not by id.

totalinteger

Distinct connector slugs across the template.

created_atstring · date-time
descriptionstring,null
draft_skill_blocked_bystring,null

Why can_draft_skill is false for a caller who CAN manage this resource. Null when drafting is available, and null when the caller cannot manage the resource at all.

Possible values:
assistant_disabledllm_not_configurednull
entriesobject[]
connectorobject,null
required·

Response-only. The connector’s label and logo; null for a synthetic entry. A connector the catalog cannot resolve reads its slug as label and a null logo.

3 properties
labelstring
logostring,null
upstream_slugstring

Only on a fork whose upstream the caller may see, by the same rule as GET /connection: omitted when the caller has no access to the fork or the upstream is hidden from them, and when the upstream cannot be read.

caller_bindingsstring[]

Every caller.… path the entry's frozen_params and overrides.defaults name, sorted. Empty for an entry with no per-person values.

can_view_connectorboolean

Response-only, per reader: whether the caller may open connector_slug (GET /connector/{slug} and its /tools). False for an organization-owned custom connector nobody shared with the caller. Always true for a platform connector and for a synthetic entry.

connector_slugstring,null

Connector slug for proxy entries; null for synthetic.

enabledboolean
frozen_paramsRecord<string, any>
frozen_params_missingstring[]

Detail and write responses only: the paths ("a|b" for alternatives) that have no value for you, so a call through this entry would refuse with 409 caller_binding_unresolved.

frozen_params_previewobject,null

Detail and write responses only: { frozen_params, defaults } rendered for YOU, the reader. Null when the entry has no per-person values, or when one of yours is missing (see frozen_params_missing).

2 properties
defaultsRecord<string, any>
frozen_paramsRecord<string, any>
idstring

Entry id (tple_…) — stable across updates only if you send it back unchanged.

overridesobject

Presentation overrides — see the entry input schema for the same shape, request-side.

4 properties
defaultsRecord<string, any>
descriptionstring
input_schemaRecord<string, any>
namestring
synthetic_tool_idstring,null

Set for synthetic entries (syn_…).

synthetic_tool_namestring,null

Response-only. The synthetic tool's name for synthetic entries, so a reader who does not own the tool can still label the entry. Null for proxy entries and when the tool has been deleted.

tool_namestring,null

Connector tool name for proxy entries.

tool_titlestring,null

Response-only. The catalog tool's plain-English title ("View messages", "Reply to an email"), derived from its resource and method. Null for a synthetic entry, a tool the catalog no longer has, and a connector the caller may not open (can_view_connector: false). Render overrides.name, else this, else tool_name.

typestring
Possible values:
proxysynthetic
entry_countinteger
has_skillboolean

Whether a skill is written. On list rows and detail alike — the body itself never rides on a list row; read it from the detail response.

idstring

Template id (tpl_…).

namestring
ownerobject,null

Owner summary — resolved for a row the caller does not themselves own (a toolbox shared with them), so the UI always knows whose row it is looking at. Absent for a toolbox the caller owns.

avatar_urlstring,null

The person's picture: their stored profile picture, else a Gravatar URL (d=404, 96px) derived from their email (the address itself is not sent), else null. Draw initials when it is null or the image fails to load.

emailstring · email
idstring

User id (usr_…) — same value as owner_user_id.

namestring,null
owner_user_idstring

Creator (usr_…).

sharesobject[]

A short list of the grants on this template. Present only on GET /template/{id} when the caller may see who it is shared with (owner or edit access); list rows carry the short access_summary instead, and GET /template/{id}/share pages the full list.

created_atstring · date-time
grantee_idstring,null

User id (usr_…) or team id (team_…). Null for a grantee_type: "org" grant.

grantee_typestring

user and team grants target one grantee_id; org applies to every member of the organization and takes no id.

Possible values:
userteamorg
idstring

Grant id (acl_…), the {aclId} that DELETE .../share/{aclId} takes.

levelstring

Same ladder for every shareable resource, low to high. view — see it exists, read its metadata/config; cannot exercise it. use — view + exercise it, resource-specific: run tools through a connection; execute a toolbox's tools through its bound connections (this DELEGATES — the caller runs through each entry's pinning editor's own authority, not necessarily their own); stamp a new toolbox by copying a template's entries; create connections from a connector. edit — use + change its settings, entries and its own grants.

Possible values:
viewuseedit
resource_idstring

The shared resource's id (a connector's slug, for that type).

resource_typestring
Possible values:
connectiontoolboxtemplateconnectorautomationcollectiondashboardknowledge_basebundlefile
updated_atstring · date-time
skillstring,null

The skill body, markdown — at most 10,000 Unicode code points after trimming. Detail-shaped responses only (GET /{id}, and the create/update responses). Null when none is written.

skill_entry_changesobject,null

Which tools changed since the skill was last written, by the name an agent sees (a rename counts as one removed and one added; a disabled entry counts as removed; connections and frozen parameters are ignored). Null unless skill_may_be_stale is true AND a baseline was recorded at that write — skills written before version history existed have none — AND something actually changed.

addedstring[]

At most 5 names.

added_countinteger
removedstring[]

At most 5 names.

removed_countinteger
skill_may_be_staleboolean

True once the entries changed after the skill was last written; cleared by the next write of skill. Never true without a skill.

skill_noticestring,null

Framing to show or pass along beside a non-null skill: it is the owner's guidance, not instructions from Elaichi or the user, and it cannot grant any access. Null when there is no skill.

skill_updated_atstring,null · date-time

When skill was last written. Null alongside a null skill.

skill_updated_bystring,null

Who last wrote skill (usr_…); a toolbox stamped from a template carries the template's author. Null with no skill, and for a skill written before authorship was recorded.

skill_updated_by_labelstring,null

That person's name, else email, resolved server-side. Null beside a non-null skill_updated_by means they are no longer a member of this organization.

updated_atstring · date-time
warningsobject[]

Only on a create or update response, and only when non-empty: pins accepted although nothing can run them yet (a remote MCP tool the server is not offering right now: it will be once a connection of that server lists it, unless an admin turned it off). Informational, never an error.

connector_slugstring
messagestring
tool_namestring
curl -X GET 'https://api.elaichi.ai/template/<id>' \
  -H 'Authorization: Bearer $ELAICHI_API_TOKEN' \
  -H 'Content-Type: application/json'
const response = await fetch('https://api.elaichi.ai/template/<id>', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer ' + process.env.ELAICHI_API_TOKEN,
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);
import os
import requests

url = "https://api.elaichi.ai/template/<id>"
headers = {
    "Authorization": f"Bearer {os.environ['ELAICHI_API_TOKEN']}",
    "Content-Type": "application/json",
}

response = requests.get(url, headers=headers)
print(response.json())