@Matt Hall Pega’s DX API PATCH /assignments/{assignmentID}/actions/{actionID} does not support separate JSON schema validation for the content page like OpenAPI/JSON-schema tools do; instead, it relies on the normal Pega validation rules after the JSON is mapped to clipboard properties. To validate customersName, you should define it as a proper Pega property (for example, Text with a max length) and then add field-level validation using an Edit Validate rule or a Regular Expression (for allowed characters, length, etc.). You can also mark it as required and set any other constraints in the section/view and in the Flow Action or Case Type “Validation” tab. When the digital channel calls the PATCH API, Pega runs these validate rules and, if something is wrong, returns a validation error in the DX response instead of committing the change. In other words, the “schema” lives in your Pega rules, not as an external JSON schema for the content object. If you need even stricter control (for example, blocking unknown or unexpected fields in content), you would have to add custom server-side logic or put an API gateway in front of Pega to enforce an external JSON schema.