Skip to main content


Triggering an Event with the SOAP, HTTP and REST services

Suggest edit Updated on January 19, 2022

If the client calls are coming from outside the cluster that is running Pega Customer Decision Hub, you can use the SOAP, REST and HTTP services to trigger Events.

Using the built-in SOAP and HTTP services

Pega Customer Decision Hub provides built-in support for triggering events with the SOAP and HTTP services. The following ryles are available:

  • Rule-Service-SOAP
  • Rule-Service-HTTP
Important: If you are planning to use the predefined SOAP or HTTP entry points in conjuction with the Event Stream service, you must create the following dynamic system setting to send the events to the Event Stream service:
  • Rule set - PegaMKT-Engine
  • Name - MKTKafkaEvents
  • Value - true

The following URL provides the WSDL for your application's Event handling SOAP Service: http://<host>:<port>/prweb/PRSOAPServlet/SOAP/PegaMKTDataMktEvent/Services?WSDL

The following is an example request triggering the AccountOpened Event, passing in the Customer's ID, their location (latitude/longitude), and information about the Event:


Using a REST service

Pega Customer Decision Hub does not provide a built-in REST service to trigger events. However, you can define one in your rule set layer and configure it to write to the Stream data set, similar to how the HTTP or SOAP services do it. For an example, see the entry point activity HandleHTTPEvent under PegaMKT-Data-Event.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us