@sujayp16991152

You can use the REST integration wizard on the consuming application. On the sample request/response page, trigger the service with correct JSON. After the correct JSON response will be received, submit it and continue following the wizard process. At the end, all the properties provided in the request/response JSON will be created.

You can walkthrough the following challenge, its applicable for non-CDH scenarios also:

https://academy.pega.com/challenge/integrating-external-customer-service-data/v3

@sujayp16991152

It would be great if you could provide more insights into which DX APIs you're referring to to be more specific recommendations. Ideally, the response should contain all the Primary fields defined in your Case type for assignment/case level DX APIs. DX APIs will return all fields configured in the report definition rule for data views. 

@sujayp16991152To consume a DX API response from one Pega application in another, use a Connect-REST rule to integrate with the DX API endpoint. Pega offers an OOTB way to handle large JSON responses without manually creating all properties. You can use the "Create Data Type from JSON" feature to auto-generate properties and classes based on the response structure. Alternatively, map the JSON directly to the clipboard using the pxConvertStringToPage function, which dynamically maps the response to a clipboard page without needing predefined properties. To simplify further, configure a data page with the REST integration so Pega automatically handles the response mapping. This approach avoids manual work while ensuring the application efficiently consumes the DX API data