---
title: "Create a notification template (V4)"
method: POST
path: "/v4/subscription/template"
tags: ["Templates"]
---

# Create a notification template (V4)

`POST /v4/subscription/template`

/v4/subscription/template

Create a custom notification template. Afterwards you can use its id as `templateId` when creating or updating alerts (only available on TRON and EVM for now).

## Request body

- union
  - object
    - `format` 'string', required
    - `message` string, required — Notification message utilizing available properties.
  - object
    - `format` 'json', required
    - `keys` object, required — Mapping of available properties (values) to custom fields (keys).

## Response `200`

OK

- Id
  - `id` string — ID of the entity.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized. Not valid or inactive subscription key present in the HTTP Header.
- `500` — Internal server error. There was an error on the server during the processing of the request.

---

[API](https://skmtc.net/tatum/apis/blockchain-data.md) · [All operations](https://skmtc.net/tatum/apis/blockchain-data/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tatum/blockchain-data/revisions/8622ee4b8fae/schema)