Author Info
Chris Malek

Chris Malek is a PeopleTools® Technical Consultant with two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.

About Chris Work with Chris
Do you need a quick way to create web services?
PeopleSoft Simple Web Services (SWS)

Introducing a small but powerful PeopleSoft bolt-on that makes web services very easy. If you have a SQL statement, you can turn that into a web service in PeopleSoft in a few minutes.

Read More & Purchase


The PeopleSoftListeningConnector is used to message between PeopleSoft instances. This would be something like PeopleSoft HR talking to PeopleSoft Campus or PeopleSoft Finance. This is what is used when delivered PeopleSoft “sync” trigger like “PERSON_BASIC_SYNC” or “USER_PROFILE_SYNC”.

You should NEVER be targeting this end-point for external integration. You should either be targeting the HttpListeningConnector or the Rest Connector for external integrations.

A common mistake I see people make is giving the PeopleSoft integration broker URL like this to someone trying to call PeopleSoft web serivces: The reason is that if you look at the “Gateway” page in PeopleSoft that page will surface that URL. However, that is never correct for external integrations. I have seen many months of wasted person hours with external systems trying to integrate and targeting the PeopleSoftListeningConnector when they should be targeting one of the other listening connectors.

This listening connector is meant for two PeopleTools systems to exchange information and it uses MIME data encoding to transfer data. No integration partner uses MIME encoding of data.

From PeopleBooks:

…using MIME multipart message type (Content-Type: multipart/related;), with a very specific internal formatting: there are two MIME parts (section), one carries the IBInfo (the parameters of the sending) and the other carries the message payload XML.

The URL pattern is: https://host:port/PSIGW/PeopleSoftListeningConnector

The security for this node type typically uses these options:

Connectivity Test

If you need to test connectivity to this handler you can do a CURL like this:


HTTP/1.1 200 OK
connection: close
content-length: 306
content-type: text/html
date: Sun, 22 May 2022 14:04:09 GMT
strict-transport-security: max-age=31536000; includeSubDomains; preload

PeopleSoft Integration Gateway
<div id="pt_pageinfo_win0" menu="PING_GATEWAY" component="PING_GATEWAY" page="PING_GATEWAY"></div>
<H1>PeopleSoft Integration Gateway</H1>
PeopleSoft Listening Connector<BR>
Status:<span id="PING_STATUS">ACTIVE</span>