Skip to main content


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

Delete Registration Pega Process Fabric Hub endpoint

Updated on November 9, 2021

The Delete Registration REST API helps you efficiently manage data in the Pega Process Fabric Hub by deleting connections with applications that you no longer need for your business processes.

You invoke the Delete Registration REST API by calling the following endpoint:

DELETE /registrations/{ID}

When you delete an application from the Pega Process Fabric Hub, you delete the relevant assignment and operator data from the Pega Process Fabric Hub and the connection between your application and the Pega Process Fabric Hub. The Registered applications landing page stops displaying the deleted application.

Before you call the Delete Registration REST API, consider the following factors:

  • You can delete an application only if the application has one of the following statuses:
    • Inactive
    • Pending-Activation
    • Activation-Failure
  • The Delete Registration REST API returns an empty response with the status code of 200 on successful connection deletion.
  • If an error occurs, the response includes an appropriate status code and error message.

The following table shows sample details for the Delete Registration endpoint:

ElementValue
Request URLhttps://vlenghydcnt17263-processfabrichub.lab.pega.com/prweb/api/ppf/v1/registrations/REG-22951
Request headersAuthorization: Bearer access token
Request bodyNot applicable
Response status200
Response bodyNot applicable

For more information, see the Swagger documentation.

  • Previous topic Deactivate Registration and Reactivate Registration Pega Process Fabric Hub endpoints
  • Next topic Data Synchronization APIs for the Pega Process Fabric Hub

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us