template_access_denied — no access to the template

A domain refusal of order creation: HTTP 403, body {"success": false, "message": "…", "reason": "template_access_denied"}. The order was not created.

The template exists, but this key is not allowed to use it: the template belongs to another account, or the key lacks the templates.read scope. A nonexistent template looks different — GET /templates/{template} returns 404, and POST /orders fails the exists validation and returns 422 with the field in errors.

Check that the template is visible to the key. A template is owned by the account, not by a specific key: a template created on the web works for the API and vice versa, but a template that belongs to another account will not open with any key. If the template is yours, the problem is scopes: automation does not include templates.write, but it does include templates.read.

GET /templates/{template} — 200 means you have access and the refusal has a different cause; 404 — the template does not exist; 403 — confirms the refusal. The list of templates available to the key — GET /templates.

• Guide: templates
• Guide: API keys, scopes, and headers
• GET /templates/{template}
• GET /templates
• 403 — insufficient permissions
• My key scopes