Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Endpoint for real-time publishing of associations

Updated on August 26, 2022

After publishing existing associations data, the remote application can immediately publish any changes to the associations. When you invoke the appropriate REST APIs, you ensure that Pega Process Fabric Hub and your remote application are always in sync. As a result, Pega Process Fabric Hub reflects accurate data about associations from your application.

You publish new associations to Pega Process Fabric Hub by invoking the following endpoint:

PUT /associations, action = "create"

You update associations in Pega Process Fabric Hub by invoking the following endpoint:

PUT /associations/{associationID}, action = "update" or "delete"

Note: As a best practice, when you handle large amounts of data, use scaling mechanisms, such as queues.

The following table shows a sample request body for the real-time endpoint:

Request URL!EPIC-123!operator!begua!Follower
Request headersAuthorization: Bearer access token
Request body
    "fromType": "case", 
    "fromID": "EPIC-123", 
    "toID": "begua", 
    "toType": "operator", 
    "action": "create", 
    "category": "Follower", 
    "createDateTime": "20210226T061741.441 GMT", 
    "createOperator": "sikhm_m", 
    "updateDateTime": "20210226T061742.441 GMT", 
    "updateOperator": "sikhm_m", 
    "ID": "kYC-123!begua!Approver"  
Response status202
Response bodyNot applicable

For more information, see the Swagger documentation and Accessing and testing Pega DX API Version 1.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us