# Create a new Notification for the corresponding Challenge

**POST /v2/Services/{ServiceSid}/Entities/{Identity}/Challenges/{ChallengeSid}/Notifications**

Create a new Notification for the corresponding Challenge
TODO: Resource-level docs

## Servers



## Parameters

### Path parameters
- **ServiceSid** (string)
  The unique SID identifier of the Service.
- **Identity** (string)
  Customer unique identity for the Entity owner of the Challenge. This identifier should be immutable, not PII, length between 8 and 64 characters, and generated by your external system, such as your user's UUID, GUID, or SID. It can only contain dash (-) separated alphanumeric characters.
- **ChallengeSid** (string)
  The unique SID identifier of the Challenge.


### Body:  (object)

- **Ttl** (integer)
  How long, in seconds, the notification is valid. Can be an integer between 0 and 300. Default is 300. Delivery is attempted until the TTL elapses, even if the device is offline. 0 means that the notification delivery is attempted immediately, only once, and is not stored for future delivery.


## Responses
### 201
Created

#### Body:  (object)
- **account_sid** (string | null)
  Account Sid.
- **challenge_sid** (string | null)
  Challenge Sid.
- **date_created** (string(date-time) | null)
  The date this Notification was created
- **entity_sid** (string | null)
  Entity Sid.
- **identity** (string | null)
  Unique external identifier of the Entity
- **priority** (string | null)
  The priority of the notification.
- **service_sid** (string | null)
  Service Sid.
- **sid** (string | null)
  A string that uniquely identifies this Notification.
- **ttl** (null | integer)
  How long, in seconds, the notification is valid.


[Powered by Bump.sh](https://bump.sh)