7. View Payload (cURL)
4 min
Inspect the raw JSON patch that will be sent to AEP before committing the update. The payload is formatted as a cURL command for easy inspection and external testing.
What is the payload?
The payload represents all profile changes made across all dynamic forms in the current session, serialized as a JSON object conforming to the target XDM schema.
Clicking View payload opens a modal showing the full cURL command — including the endpoint URL, request headers, and JSON body — that would be sent to the DSN Streaming Inlet.
Payload structure
Section | Contents |
|---|---|
header | Schema reference, dataset ID, and message ID |
body.xdmMeta | XDM schema descriptor |
body.xdmEntity | The profile patch with all modified field values |
Postman size limitation
⚠️ When copying the cURL command for use in Postman, very large JSON payloads may be truncated by Postman's paste buffer limit. The paste appears to succeed but the JSON body is silently cut off, resulting in a malformed request.
Workaround options:
- Save the JSON body to a local file and reference it in cURL with --data @payload.json
- Use the Update profile button directly from the tool instead of going through Postman
Use cases for payload inspection
- Verify the exact field paths and values before committing
- Share the payload with a customer to explain the XDM data structure
- Replay the update in a different sandbox via Postman or a CI/CD pipeline
- Debug unexpected update results by comparing the payload to the refreshed profile