Pega Digital Experience delivers a unified and branded experience across multiple channels. The Pega Digital Experience (DX) API is a collection of model-driven REST API endpoints that allow you to programmatically view, create, and update cases and assignments. This enables developers to create custom front-end experiences for Pega Platform™ applications without having to embed business logic in each individual channel. P

DX API version 2 is primarily focused on view-based authoring. It enables you to manage data views, explore metadata, and retrieve specific fields via data view endpoints.It is important to ensure that applications are compliant with the DX API. Compliance ensures that developers can create suitable front-end components using their preferred UI frameworks, aligning with the center-out architecture approach. Here are some best practices to follow when designing applications with DX APIS:

• Harnesses should use a screen layout as the main container.
• Visibility expressions must only reference when rules.
• Sections should be auto-generated.
• Sections should use one of the following layouts:
  • Table
  • Dynamic layout
  • Repeating dynamic layout (not sourced from data pages)
  • Embedded section
• If a flow action involves editable pages (such as named pages, thread-level data pages, or requestor-level data pages), the edited values won’t be available in post-processing data transforms or activities. In these cases, use auto-populated properties (that get data from data pages) and savable data pages during flow action post-processing.
• Always configure applications to use optimistic locking.
• DX API v2 testing requires authorization to generate sample endpoint responses, which means you’ll need an OAuth 2.0 client registration data instance.

DX API reference with sample payload for your reference: