Skip to content

Commit 55add97

Browse files
authored
Update 16/umbraco-cms/reference/webhooks/README.md
1 parent d4a1ead commit 55add97

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

16/umbraco-cms/reference/webhooks/README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,9 @@ Each webhook event sends a JSON payload. The following types of payloads are ava
5757
#### Legacy
5858

5959
This is the current default but will be removed in a future version. Legacy payloads follow the format used before version 16. They are inconsistent and may include data that should not be exposed or has been superseded (e.g., use of `int` instead of `Guid`).
60-
- Minimal: This will be the default in v17+. This version of the payloads will only contain information to indentify the resource in question. For most resources this will be it's unique identifier. Some events might require more information. For example: the payload for the document publish event will also contain all cultures that were published at that point in time.
60+
#### Minimal
61+
62+
This will become the default in version 17 and later. Minimal payloads include only essential information to identify the resource. For most events, this means a unique identifier. Some events may include additional data. For example, a document publish event also includes the list of published cultures.
6163
- Extended: These are new payload types that are available for some but not all events that gives you all relevant information regarding the event. Some information, like user/member names and emails, are not part of the payloads for security/privacy concerns. In cases where an extended payload is not present for an event, the minimal will be used as fallback.
6264

6365
You can change which payload type is used by

0 commit comments

Comments
 (0)