---
title: "POST /notification-configurations"
method: POST
path: "/notification-configurations"
---

# POST /notification-configurations

`POST /notification-configurations`

Creates a notification configuration. A configuration is a connection between an event type and a destination that you have already created.

## Request body

- object
  - `EventType` 'DEVICE_COMMAND' | 'DEVICE_COMMAND_REQUEST' | 'DEVICE_DISCOVERY_STATUS' | 'DEVICE_EVENT' | 'DEVICE_LIFE_CYCLE' | 'DEVICE_STATE' | 'DEVICE_OTA' | 'DEVICE_WSS' | 'CONNECTOR_ASSOCIATION' | 'ACCOUNT_ASSOCIATION' | 'CONNECTOR_ERROR_REPORT', required — The type of event triggering a device notification to the customer-managed destination.
  - `DestinationName` string, required — The name of the destination for the notification configuration.
  - `ClientToken` string — An idempotency token. If you retry a request that completed successfully initially using the same client token and parameters, then the retry attempt will succeed without performing any further actions.
  - `Tags` object — A set of key/value pairs that are used to manage the notification configuration.

## Response `201`

Success

- CreateNotificationConfigurationResponse
  - `EventType` 'DEVICE_COMMAND' | 'DEVICE_COMMAND_REQUEST' | 'DEVICE_DISCOVERY_STATUS' | 'DEVICE_EVENT' | 'DEVICE_LIFE_CYCLE' | 'DEVICE_STATE' | 'DEVICE_OTA' | 'DEVICE_WSS' | 'CONNECTOR_ASSOCIATION' | 'ACCOUNT_ASSOCIATION' | 'CONNECTOR_ERROR_REPORT' — The type of event triggering a device notification to the customer-managed destination.

## Other responses

- `480` — AccessDeniedException
- `481` — ValidationException
- `482` — InternalServerException
- `483` — ConflictException
- `484` — ThrottlingException

---

[API](https://skmtc.net/aws/apis/iot-managed-integrations.md) · [All operations](https://skmtc.net/aws/apis/iot-managed-integrations/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/aws/iot-managed-integrations/versions/d043c13c812a/schema)