API testing reinvented

for SAP systems

API testing – definition

It’s a type of software testing that involves testing application programming interfaces (APIs) directly and as part of integration testing to determine if they meet expectations for functionality, reliability, performance, and security.


API = Application Programming Interface

Simply speaking

API testing verifies the application logic by invoking the application interface with a given request and validating the response.

Michał Kowalczewski

CTO & Co-Founder, Int4

Why does standard API testing not work for SAP centric systems?  

There are some crucial differences comparing SAP to the not out of the box IT solutions?

SAP software is just customized, not developed from scratch. Therefore, the testing needs are different from than in the development projects.

Digital transformation

Requires much faster adaptation and more robust integration with other systems to react to changing business environments. 

This means deploying more interface changes in a shorter time.

Scenarios Integration

Most integration scenarios with SAP are asynchronous. This allows for better performance, transactional handling, and better monitoring, but the classic-API testing based on the response makes no sense.

Automated test creation

SAP S/4HANA (and other SAP business systems) almost always are integrated with other by central integration platforms (ESB) like SAP PO, SAP CPI, or non-SAP ones (like Dell Boomi)

Which means that the test case creation is a laborious process as the exchanged messages to/from SAP need to be collected manually. 

What is SAP API testing?

At Int4, we focused on user-friendly SAP API testing for more than 10 years now. 

Gradually, we have transformed the obvious shortcomings and differences between API testing and SAP API testing into Int4 IFTT key features. 

We succeeded in this because our solution was  fully tailored to SAP system testing from day one.

Transport Layer Testing


Functional S/4HANA backend system testing


SAP API testing

In SAP S/4HANA integration takes place via the integration platform. 

However the development and customization of standard SAP solution take place within the Integration Platform and the S/4HANA backend system.

At Int4, we focused on user-friendly SAP API testing for more than 10 years now. 

Therefore in most scenarios, it doesn’t make sense to test them stand alone. The real validation of the integration scenario works when we test the integration platform and the SAP S/4HANA interface implementation together.

Fact: SAP API’s are asynchronous

This is how



Let’s talk!

Our Sales Team is here to help you and dispel all your doubts. Book a demo and let us present to you the Int4 IFTT tool possibilities.

Business use cases

Problem to solve:

  • No response in the asynchronous pattern
  • -> It can’t be validated
  • -> No place for the classical API testing approach


Int4 IFTT validates the integration platform output message (eg. an IDoc or XML). 

It might not be enough to finalize the testing at this stage. This is because the interface logic and rules are also in SAP S/4HANA. 

Int4 IFTT has a unique concept to validate final documents posted by interfaced scenarios (like sales orders or invoices).

Problem to solve:

  • Lack of test data
  • -> Missing data prepared manually or extracted by complicated proxy techniques
  • -> Tons of extra effort (and $)


Int4 IFTT connects to the integration platform and creates the test cases in seconds by reusing already exchanged messages and corresponding documents. 

In Int4 IFTT, the test case data is an incoming message, and the output message and final business document in S/4HANA formulate the validation rules. 

Virtualization of EDI and legacy applications for SAP API testing 

Critical issue:

  • Access to third-party systems or partners (eg. EDI). SAP teams have to work independently and test themselves the changes that occurred only in SAP.

Classic approach:

Service virtualization is a separate class of software provided on the internet protocols layers, so it is supportive for any technology.


Int4 IFTT has built-in service virtualization. Because Int4 IFTT is tailored for SAP, it skips the connectivity layer and virtualizes the sender/receiver system directly on the integration platform. There is no need to replicate the business logic of the service, as Int4 IFTT will simply record & playback it.

Int4 IFTT unlocks huge potential in SAP testing automation. In addition to the UI automation, it enables the API testing that was mostly reserved for non-SAP solutions. 

In this way, you can secure your projects better, like SAP S/4HANA transformation or integration platform migration and enable continuous testing in the area of SAP integration in your daily system maintenance activities.

Learn more about Int4 IFTT

Explore a one-step solution for all your SAP API testing scenarios. Visit our website and find the details or request a live demo with one of our specialists. 

New call-to-action

We deliver.

Look at our projects
Glencore S/4HANA conversion - Case Study - Int4
Int4 Shield

Glencore: S/4HANA conversion

Glencore AG – top commodity trader with oces and mines all over the world, founded in the 1970s. One of the world’s largest globally diversified natural resource companies. Listed in London Stock exchange.

Learn more

Virtualize and Automate Your SAP Testing

Using Int4 IFTT


Testing SAP APIs

Strategy and Execution