Please provide your thoughts on PEGA API

We got notified by API monitoring team that following path are API

  • /prweb/PRServlet/{33}/!OpenPortal_RequestorPortalOOTB
  • /prweb/PRServlet/{33}/!OpenPortal_AdminPortalOOTB
  • /prweb/PRServlet/{33}/!PopupThread0
  • /prweb/PRServlet/{33}/!TABTHREAD
  • /prweb/PRServlet/{33}/!OpenPortal_pxAdminStudio

As per my understanding this are URL to access pega portals and not API’s

can you please provide some document or information to prove this are not api’s

if this are api’s then how/where it is configured

@saurabhj16881453 The URLs you listed above don’t look like Pega APIs. It typically contains “api” in the URL - e.g. https://stage-clone-XXX.XXX.XXX/prweb/**api**/v1/pegaunits/execute?AccessGroup=XYZ

Have you reviewed the Pega API landing page? It shows a list of Pega APIs. They are ready to use for different purposes.

As an example, I have written one article that shows how to use one of the Pega APIs to create cases. Create case using Pega API (POST /cases) | Support Center

You can also open “api” Service REST rules and verify the end-point URLs.

e.g.