Using real-time container APIs
This section provides information on the APIs available for use with Real-Time Containers.
Pega Customer Decision Hub
When invoked, each API sets one of the following HTTP status codes in its response:
- 200 - Successful invocation
- 400 - Bad request
- 500 - Internal error
- Triggering a real-time container with the Container REST service
- Making custom Strategy Result properties available for real-time container data flows
- Capturing responses to actions triggered by a real-time container
- Accessing a customer's interaction history with the CustomerOfferHistory REST service
- Capturing clicks on the click-through URL
Previous topic Creating a real-time container Next topic Triggering a real-time container with the Container REST service