Question
Kavileswar
IN
Last activity: 7 Sep 2022 22:28 EDT
Why does Pega 8.7 platform add "api" in all Service endpoint URLs
Why does Pega 8.7 platform changed Base Path by adding "api"
basePath: /prweb/api/v1
In earlier Versions we had not seen api in all Service REST end point URLs
Do we have any reason for this , any impact if not include api
CGI
US
For each resource URI, api indicates the service package, v1 indicates the service version, and the text after v1/ indicates URI templates. Because each resource URI contains a distinct URI template, each resource URI is mapped to a different service REST rule.
For more info you can refer to below link
Kavileswar
IN
Am talking about Application Developed REST APIs but not Pega API built in REST APIs. Please find below sample url
...prweb/api/SCASPENAPI/V1/Interactions
SCASPENAPI is my Service Package , here what is the significance of "api" , why does add it
We know that api is the service package in built in REST APIs (OOB) hosted by Pega
CGI
US
As far as I know there is no specific significance of "api" keyword.
To call a REST service rule, use "api" in the URL, and append the three-part key to the rule to the URL.
https://appname.pegacloud.io/contextroot/api/packageName/version/resourcepathURL
Although you can still call a REST service by specifying /PRRestService, as a best practice, use api.
For more detailed explanation please refer below Pega docs link.
https://docs-previous.pega.com/data-management-and-integration/86/invoking-rest-service-rule
Pegasystems Inc.
IN
@Kavileswar What if you remove the 'api' keyword and create your url - does it work then?
Pegasystems Inc.
IN
@Kavileswar I am speculating it to be a generic thing, which Pega internal functions may have added during url construction - when you save as. It's not necessary to have "api". Maybe you can raise a ticket with the product team for more info, as this is not the case in older versions.