Skip to main content


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

Capturing responses to actions triggered by a real-time container with the CaptureResponse service

Updated on February 17, 2020

Call the CaptureResponse REST service to capture responses to actions triggered by a real-time container. You can create the service request using the POST method.

Task IDTask-050504
Primary roleSenior Decision Architect
Secondary roleN/A
Tertiary roleN/A

Service URL

http://<host>:<port>/prweb/PRRestService/PegaMKTContainer/V2/CaptureResponse

Note: To automatically initiate the first action in the service request, use the following URL pattern:
http://<host>:<port>/prweb/PRRestService/PegaMKTContainer/V2/CaptureResponse/Initiate

Request parameters

For the request, the service expects a JSON Object with the action received.

Sample request

{
"ContainerName":"TopOffers",
"CustomerID":"17",
"RankedResults": [{
"Name": "PlatinumCardOffers",
"Issue": "Sales",
"Group": "CreditCards",
"Rank": 1,
"CampaignID": "NBA",
"InteractionID": "-563481321460449721",
"Outcome": "Accepted",
"Behaviour": "Positive"
"Channel": "Web",
"Direction": "Inbound"
"Journey":"",
"JourneyStage":"",
"JourneyStep":""
}]
}

Service response

For the response, the service returns a JSON object with the following attributes:

  • Status - The status of the request, for example, OK or ERROR.
  • Message - If the request failed, this parameter provides the description of the error.

Sample response

{
"Status": "OK",
"Message": "Response captured successfully"
}

Response codes

  • 200 - Successful invocation
  • 400 - Bad request
  • 500 - Internal error

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