> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/templates/delete-transaction-template-by-templateuid.md). # Delete transaction template by templateUId Delete transaction template by templateUId A template whose type an active service status rule sends is kept while any such rule is active, whichever language it is written in: deleting it is refused with a conflict, which is resolved by switching off every rule that sends the type, pointing those rules at another type, or deleting them. Every language of the type is held, not the tenant's own alone: a rule falls back to the tenant's own language when the customer's preferred language has no text, and changing the tenant's language moves that floor to a language the tenant may have written nothing in. The hold covers status rules alone. The types the timeline event message and the portal link message compose from carry no rule, so deleting one is not refused and those sends then refuse until the text is written again. TEMPLATE reaches every template. SERVICE\_CONFIG reaches the templates of a service template type only — a type the platform's own catalog on the `/metadata/templates` endpoint does not list, which is what templateOrigin SERVICE lists, the seven types the service module sends under fixed names and every other type the tenant has created alike — because a service message text is service configuration. A caller holding SERVICE\_CONFIG and not TEMPLATE is refused with a 403 on a template of a platform type, and nothing is deleted. A tenant-wide ADMIN grant counts as every permission. Required permissions: TEMPLATE, SERVICE\_CONFIG ```json {"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Notifications","description":"Notifications"},{"name":"Templates","description":"Templates"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"authToken":[]},{"accessToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}}},"paths":{"/tenants/{tenantUid}/templates/{templateUid}":{"delete":{"summary":"Delete transaction template by templateUId","tags":["Templates","Notifications"],"responses":{"200":{"description":"OK"},"404":{"description":"Not Found"},"409":{"description":"Conflict. The template is a text for a type an active service status rule sends, and every language of such a type is kept while any rule that sends it is active — which is resolved by switching off every rule that sends the type, pointing those rules at another type, or deleting them."}},"operationId":"delete-tenant-template-templateUid","description":"Delete transaction template by templateUId\n\nA template whose type an active service status rule sends is kept while any such rule is active, whichever language it is written in: deleting it is refused with a conflict, which is resolved by switching off every rule that sends the type, pointing those rules at another type, or deleting them. Every language of the type is held, not the tenant's own alone: a rule falls back to the tenant's own language when the customer's preferred language has no text, and changing the tenant's language moves that floor to a language the tenant may have written nothing in.\n\nThe hold covers status rules alone. The types the timeline event message and the portal link message compose from carry no rule, so deleting one is not refused and those sends then refuse until the text is written again.\n\nTEMPLATE reaches every template. SERVICE_CONFIG reaches the templates of a service template type only — a type the platform's own catalog on the `/metadata/templates` endpoint does not list, which is what templateOrigin SERVICE lists, the seven types the service module sends under fixed names and every other type the tenant has created alike — because a service message text is service configuration. A caller holding SERVICE_CONFIG and not TEMPLATE is refused with a 403 on a template of a platform type, and nothing is deleted. A tenant-wide ADMIN grant counts as every permission.\n\nRequired permissions: TEMPLATE, SERVICE_CONFIG"}}}} ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flowretail.com/docs/developers/api-documentation/templates/delete-transaction-template-by-templateuid.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.