Templates

List Transfer Templates

List the transfer templates this caller may invoke (LaaS-26, LaaS-78).

Two tiers, in resolution order. The **platform** tier is operator-defined, deploy-time JSON and reflects the registry command-api validated at startup. The **tenant** tier is this caller's own runtime-authored templates (``tnt.{tenant}.{name}``), read from the caller's own partition — so another tenant's templates are not merely filtered out of this list, they are unaddressable. Each entry carries its ``template_version`` and ``content_hash`` (the tamper-bound attribution stamped on every obligation an invocation produces), plus ``tier`` and ``status``.

RETIRED tenant templates are listed and marked. Retiring gates new execution, never observation — and the id has to stay resolvable for attribution anyway.

⚠️ **The tenant tier is capped at 100 entries here and the cap is not silent:** this route's published shape is a bare ``items`` array with no cursor (LaaS-26), so there is nowhere to hand back a continuation. A tenant that outgrows it reads the paginated operator listing (``GET /v1/operator/tenants/{tenant}/transfer-templates``) instead, and giving this route a cursor is a contract change for whoever needs it first.

Respostas

Get a Transfer Template

Get one transfer template by id — platform tier, then the caller's own.

⛔ A template belonging to another tenant answers **404**, identically to one that never existed: the tenant is a segment of the partition key, so the two are one DynamoDB miss and the response cannot differ in status, body or headers (LaaS-78 AC3).

Parâmetros

Respostas