Templates

Transfer template ownership

Changes owner_user_id — and nothing else. Every existing grant is left exactly as it was. Allowed for the current owner only — no template:manage fallback.

post/template/{id}/transfer

Request

  • Base URL: https://api.elaichi.ai
  • URL: https://api.elaichi.ai/template/{id}/transfer
  • Auth: HTTP bearer

Path parameters

idstring required

Template id (tpl_…).

Headers

X-Organization-Idstring

Target organization (org_…). Required for cookie/session auth on org-scoped routes; optional for API tokens, which carry their organization, and rejected when it names a different one.

Request body

owner_user_idstring required

New owning member (usr_…).

Response

OK

idstring

Template id (tpl_…).

namestring
descriptionstring nullable
owner_user_idstring

Creator (usr_…).

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.

entry_countinteger
created_atstring date-time
updated_atstring date-time
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.

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.

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.

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_manageboolean

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

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_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}.

access_via'owner' | 'direct' | 'team' | 'org'

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.

Changes

No recorded changes to this operation across all 1 revision of this API.