<commit_before>---
title: Notification Messages
---

## Overview

Notification Messages are generally used by Endpoints to convey information to the owner of the store (or one of their employees.) These Messages are typically generated in the context of an Endpoint Service Request and should always be sent with a HTTP Status Code of `200`.

***
Notification Messages can be mapped to Endpoints just like any other Message. By default they are also automatically converted into Log Entries.
***

## Message Types

### Info

This Message type is for communicating interesting information from Endpoint Services. It is common for this type of Message to be sent in response after an Endpoint processes an inbound Message.

---notification:info---
```json
{
  "message": "notification:info",
  "message_id": "518726r84910000001",
  "source": "incoming",
  "payload": {
    "subject": "Tracking number assigned",
    "description": "Shipment has been given a tracking #123443-5242."
  }
}
```

### Warn

Use this Message type to indicate that a Service executed successfully but that there may be a potential problem that's worth investigating.

---notification:warn---
```json
{
  "message": "notification:warn",
  "message_id": "518726r84910000002",
  "source": "accepted",
  "payload": {
    "subject": "Unable to verify address",
    "description": "Shipment #H123456 contains an address that was unabled to be verified. We have shipped the package anyways but it may not get there!"
  }
}
```
<commit_msg>add source sample.<commit_after>---
title: Notification Messages
---

## Overview

Notification Messages are generally used by Endpoints to convey information to the owner of the store (or one of their employees.) These Messages are typically generated in the context of an Endpoint Service Request and should always be sent with a HTTP Status Code of `200`.

***
Notification Messages can be mapped to Endpoints just like any other Message. By default they are also automatically converted into Log Entries.
***

## Message Types

### Info

This Message type is for communicating interesting information from Endpoint Services. It is common for this type of Message to be sent in response after an Endpoint processes an inbound Message.

---notification:info---
```json
{
  "message": "notification:info",
  "message_id": "518726r84910000001",
  "source": "incoming",
  "payload": {
    "subject": "Tracking number assigned",
    "description": "Shipment has been given a tracking #123443-5242."
  }
}
```

### Warn

Use this Message type to indicate that a Service executed successfully but that there may be a potential problem that's worth investigating.

---notification:warn---
```json
{
  "message": "notification:warn",
  "message_id": "518726r84910000002",
  "source": "mandrill.order_confirmation",
  "payload": {
    "subject": "Unable to verify address",
    "description": "Shipment #H123456 contains an address that was unabled to be verified. We have shipped the package anyways but it may not get there!"
  }
}
```

{'fraction_non_alphanumeric': 0.09545753785385122, 'fraction_numerical': 0.03489137590520079, 'mean_word_length': 4.378761061946903, 'pattern_counts': {'":': 24, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4668179', 'n_tokens_mistral': 871, 'n_tokens_neox': 791, 'n_words': 380}