---
title: "Outgoing webhook notification endpoint"
method: POST
path: "/v1/notification"
tags: ["Receive a notification"]
---

# Outgoing webhook notification endpoint

`POST /v1/notification`

Outgoing webhook endpoint to send notifications about changes on different entities within Enfuce system. This webhook needs to be implemented by a 3rd party system in order to get notifications. Enfuce is expecting a response within 1000 ms.

## Request body

- NotificationBody
  - `id` string, required — Unique ID for a notification assigned by Enfuce
  - `type` 'ACCOUNT' | 'CARD' | 'PIN' | 'TRANSACTION' | 'AUTHORIZATION_HOLD' | 'TOKENIZATION' | 'EMVSCRIPT' | 'INVOICE' | 'FRAUD_CASE', required — Corresponds to the entity represented in other parts of Enfuce API. **Note:** The `INVOICE` enum is available only for fleet cards.
  - `branchCode` string — Your Institution Identifier assigned by Enfuce. For example, this can be used to determine the Sender ID for SMS messages.

## Response `201`

A new notification event created

- ResourceResponse
  - `description` string — Short description of the result of the action
  - `id` string — Will contain the ID of the resource that has been created or updated

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Customer does not exist
- `500` — Internal server error

---

[API](https://skmtc.net/enfuce/apis/transfer-api.md) · [All operations](https://skmtc.net/enfuce/apis/transfer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/enfuce/transfer-api/revisions/dc4a41118f80/schema)