• Get Case operation:

                  >> what is the pattern of input parameter {id} to get the case details ? Is it Case Id or Inskey?.

It must be InsKey and since that would contain a space character, you need to URL encode it.

      >> we can call the API operations directly from external application with out alter the existing mechanism of get case api operation, but how do we keep needed attributes on response structure instead complete JSON format of service page as I would like to send  status of object to external request.

At this point we don't have a filter mechanism on this API. It returns all the case details and you cannot customize it.

Update case operation:

    Unable to update the case status by using REST api since getting the below exceptions.

          1)    MyServicePage.pxObjClass (Pega-API-CaseManagement-Case)InvalidClassForInstance Abstract.

Never seen that error before. Is it only in the logs?

2)  Getting HTTP Status code :403 , Here is the response , "pxObjClass":"Pega-API-CaseManagement-Case" ,"errors":[ { "ID":"Pega_API_020" ,"message":"Missing If-Match request header" ,"pxObjClass":"Pega-API-Error" } ] }

As the error indicates, your request is missing If-Match header. This header is mandatory to prevent stale updates. The value of this header must be equivalent to the value in the ETag response header of Create Case or Get Case APIs.

Hi,

You can get the If-Match value from the header in the response of your REST call (in the bottom of the Swagger page):

1) Make your REST call with a dummy If-Match value

2) Retrieve the ETag from the response (N.B. this ETag can be retrieved from any method call on this particular case, e.g. GET /cases/{ID} is also working)

3) Enter the ETag value in the If-Match input

4) Try it out

You can get the requestBody input structure calling the GET /cases/{ID} method

You have to reuse the content parameter value

My 2 cents,

Gilles