---
title: "Get Notification Templates"
method: GET
path: "/notifications/templates"
tags: ["Notifications"]
---

# Get Notification Templates

`GET /notifications/templates`

## Request

- Base URL: `https://api.smartroutes.io/v2`
- URL: `https://api.smartroutes.io/v2/notifications/templates`
- Auth: none declared

Lists the SMS and email notification templates set up for the depot your API key belongs to. Use it to look up the template `id`s you pass in `templates` to `POST /notifications/schedule/orders`.

The response is a plain JSON array, not wrapped in a key. Each entry has `id`, `type` (`SMS` or `EMAIL`) and `name`. Deleted templates are left out, and the list is returned in full, with no paging. Templates are created and edited in the SmartRoutes web app, not through the API.

## Response `200`

Successful response

## Other responses

- `403`: Forbidden. Returned for rate-limit exhaustion (`name = FORBIDDEN`, with `details.retry_after_seconds` and `Retry-After` header) and permission gate failures (`name = PERMISSION`). Inspect `name` to disambiguate. Send `x-sr-api-features: rate-limit-429` to receive `429 RATE_LIMIT_EXCEEDED` for the rate-limit case instead, leaving `403` to mean permission failures only — see [API Features](#section/Getting-started/API-Features).
- `429`: Rate limit exceeded (`name = RATE_LIMIT_EXCEEDED`). **Only returned to callers that opt in** with the `x-sr-api-features: rate-limit-429` request header; without it the same condition returns `403` with `name = FORBIDDEN` and an otherwise identical body. See [API Features](#section/Getting-started/API-Features).
- `500`: An unexpected server error occurred. The body carries only `name` and `description`: internal details are never returned.

---

[API](https://skmtc.dev/smartroutes/apis/smartroutes-api.md) · [All operations](https://skmtc.dev/smartroutes/apis/smartroutes-api/llms.txt) · [OpenAPI document](https://skmtc.dev/smartroutes/apis/smartroutes-api/revisions/a7ea507afac7?raw)