Skip to Content
Technical Articles
Author's profile photo Santhosh Kumar Vellingiri

SAP CPI – HTTP Tracing using Own Echo Service

I often test the API(s) required for Interface development in postman before using them in SAP CPI IFlow. Postman gives me the flexibility to see the Raw HTTP request that worked successfully to invoke the API. I wish there was a possibility in SAP CPI to view the Raw HTTP request similarly.

Because it’s not there yet, I end up using HTTP Bin which replies the actual request message as a response for various HTTP Methods for sniffing. Other options are to use the Request Catcher as explained in the Blog How to sniff SAP CPI and SAP PO requests or use mitmproxy as explained in the HTTPS tracing and debugging: (4) Cloud to cloud (using Cloud Foundry) blog. Each method has it’s own merits, I won’t discuss it here.


Often I use HTTB Bin or Request Catcher from SAP CPI or SAP APIM for tracing HTTP traffic. In use cases where I had to inspect the OAUTH Flow, JWT Token Flow, OAUTH2SAMLBearer assertion, etc I had no option to anonymize security artifacts,  but at the same time concerned using an Internet service to inspect it. So I wrote a Node JS application that act as an Echo Service and deployed it to the SAP Cloud Platform. With this set-up, I no longer worry about the data sent for HTTP tracing.

I thought to share it with the community so it could be of use to someone someday.

How to Deploy the Echo Service Application

  1. Download or Clone Echoservice from Git repository
  2. Open Command prompt and navigate to the Echoservice folder in the repository.
  3. Login to Cloud Foundry
    cf login -a​

  4. Push the APP to Cloud Foundry.
    (Change the App Name and route from manifest.yml if not available in your region)

    cf push​

  5. Verify the deployment and fetch App URL
    cf apps​

How to use in IFlow

Update the integration flow Receiver connection details with Echoservice URL.


Invoke the SAP CPI Interface from postman or from the Sender system with trace mode turned on. Upon message execution, you will find the EchoService reply Original request in the below format.

	"uri": "<URL Path of http Call>",
	"method": "<HTTP Method>",
	"headers": {
		"<Request Header Name>": "<Request Header Value>"
	"params": {
		"<Query Parameter Name>": "<Query Parameter Value>"
	"data": "<Request Body>"

Or you can find the HTTP Traffic information in CF Logs as below.

cf logs echoservice --recent | findstr /L APP/PROC/WEB/0

In the next blog SAP APIM – Route Service plan to Manage Cloud Foundry Apps, I will show how to manages this Cloud Foundry Micro Service using SAP API Management Route service.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Fatih Pense
      Fatih Pense

      Another nice blog post. Thanks for sharing! Noted it down for the case of sensitive HTTP tracing needs.


      Author's profile photo Saurabh Kumbhare
      Saurabh Kumbhare

      Hi Guys,


      Is there a way to find which IP address was used by CPI to send requests for each transmission ?




      Author's profile photo Rajesh PS
      Rajesh PS

      Santhosh Kumar Vellingiri


      Hi Santosh - Nice Blog cheers.

      I wanted to check regards X-dynaTrace in http header generated and sent to consumer application. Though headers are disabled at SAP CPI end due to this invalid chars the message is failed to consume at end application.

      Flow looks like SAP CPI -> EMP (kafka) -> Consumer app(.NET)


      Thanks Santhosh Kumar Vellingiri