Shaping the body with a mapping profile
Without a mapping profile you receive the standard body shown for each event on Events. A mapping profile on the subscription changes that:
- Canonical keeps the standard body. You can still wrap it in a property, for example
{"data": {...}}. - Field map builds your own body: you choose the output keys for the order fields and for each line array, and where each value comes from (an event field, a fixed value or a default). You can choose whether a missing value is sent as
nullor left out. Field maps can produce JSON, CSV or both. - JSON wrapper. An optional property name that wraps the complete JSON body once, after mapping and before signing. The signature always covers the body exactly as sent.
Catalog batches always use the standard JSON body. A canonical mapping profile may only wrap it in a property.
Checking a profile
Save the profile, then use Preview in the developer portal to see the exact body your endpoint will receive, and Validate to check the mapping.
A retry or replay builds the body with the subscription's current mapping profile, so a fix to the profile applies to deliveries you retry afterwards. Catalog batch parts are the exception: they are sent byte for byte the same every time.