Skip to main content

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

About Connect HTTP rules

Updated on August 10, 2022

The HTTP integration interface supports interactions between your Pega Platform applications and other systems through HTTP.

Important: Connect HTTP rules are deprecated. After an upgrade to Pega Platform 8.6 and later, you cannot create new Connect HTTP rules. However, existing Connect HTTP rules will continue to function. Use Connect REST rules instead. For more information, see Creating a REST integration by using the Create REST integration wizard.

The following tabs are available on this form:

Use Connect HTTP rules when you want your application to send XML or string data (text) as messages to an external system without the need to comply with messaging standards or protocols like SOAP.

Connect HTTP rules provide a low-overhead, stateless alternative to SOAP.


To list the Connect HTTP rules in your application, use the Application Explorer or click ConfigureIntegrationConnector Definitions & Simulations.

To list all Connect HTTP rules that are available to you, use the Records Explorer.


To create Connect HTTP rules directly in your application, click Create Integration-ConnectorsConnect HTTP.

The HTTP connector supports sending and receiving attachments with the HTTP response message. For more information, see Pega Community article How to configure a SOAP or dotNET connector to send or receive SOAP with attachments.

Where referenced

Connect HTTP rules can be referenced in an Integrator shape of a flow rule, or on the Definition tab of a Data Page rule, as the source of data for the contents of the data page.


A Connect HTTP rule is an instance of the Rule-Connect-HTTP rule type. Connect HTTP rules belong to the Integration-Connectors category.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us