---
title: "Changes to Create a notification"
method: POST
path: "/notification"
---

# Changes to Create a notification

`POST /notification`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 1 of 5 revisions.

- **2026-09-11** `a3ef7e6cc6ac`: 3 breaking, 14 warning, 6 info

## Changes

- **2026-09-11** `a3ef7e6cc6ac`: 3 breaking, 14 warning, 6 info
  - removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13` from the `payload` request property `anyOf` list
  - the response property `payload` became nullable for the status `200`
  - the response property `payload` became optional for the status `200`
  - added the new `SERVICE_UNAVAILABLE` enum value to the `code` response property for the response status `400`
  - added the new `SERVICE_UNAVAILABLE` enum value to the `code` response property for the response status `401`
  - added the new `SERVICE_UNAVAILABLE` enum value to the `code` response property for the response status `402`
  - added the new `SERVICE_UNAVAILABLE` enum value to the `code` response property for the response status `403`
  - added the new `SERVICE_UNAVAILABLE` enum value to the `code` response property for the response status `404`
  - added the new `SERVICE_UNAVAILABLE` enum value to the `code` response property for the response status `409`
  - added the new `SERVICE_UNAVAILABLE` enum value to the `code` response property for the response status `500`
  - added the new `TOO_MANY_REQUESTS` enum value to the `code` response property for the response status `400`
  - added the new `TOO_MANY_REQUESTS` enum value to the `code` response property for the response status `401`
  - added the new `TOO_MANY_REQUESTS` enum value to the `code` response property for the response status `402`
  - added the new `TOO_MANY_REQUESTS` enum value to the `code` response property for the response status `403`
  - added the new `TOO_MANY_REQUESTS` enum value to the `code` response property for the response status `404`
  - added the new `TOO_MANY_REQUESTS` enum value to the `code` response property for the response status `409`
  - added the new `TOO_MANY_REQUESTS` enum value to the `code` response property for the response status `500`
  - the request property `payload` became nullable
  - the request property `payload` became optional
  - added the new `ms-teams` enum value to the request property `provider`
  - added the non-success response with the status `429`
  - added the non-success response with the status `503`
  - removed `subschema #1, subschema #2, subschema #3, subschema #4, subschema #5, subschema #6, subschema #7, subschema #8, subschema #9, subschema #10, subschema #11, subschema #12, subschema #13` from the `payload` response property `anyOf` list for the response status `200`

---

[Operation](https://skmtc.dev/openstatus/apis/openstatus-api/docs/notification/post.md) - [API](https://skmtc.dev/openstatus/apis/openstatus-api.md) - [Page](https://skmtc.dev/openstatus/apis/openstatus-api/changes/notification/post)