Create an API in SAP API Management to upload file without using Postman
WRITTEN BY
This is my first blog post. For the past few months, I have been working on APIs as part of my work. An API is a software intermediary that allows two applications to talk to each other and also various policies can be applied to these APIs. I have created APIs in ‘Create in API designer’ component of SAP API Portal and tested various pre-packaged APIs to understand how they behave.
Introduction:
This blog post describes how to design API to upload file from your system to target system without using Postman. I have configured one iflow in SAP CPI with HTTPS on sender side and FTP adapter on receiver side. I have triggered that iflow from SAP API management to send file to target end point of iflow.
Prerequisites:
Access to SAP API Portal and SAP CPI (Cloud Platform Integration).
Host server url.
Target server url.
Steps to be followed to upload file.
Configure an iflow in SAP CPI with HTTPS on sender side and FTP adapter on receiver side. FTP adapter can be configured to send file to DriveHQ as it provides virtual FTP server to store files. Deploy the iflow and copy the end point.
Note: Keep the Post method end point same as CPI iflow end point and don’t add that end point in target server url, it will add Post method end point and trigger an iflow.
Conclusion: SAP API Management supports API-led integrations across various parties and systems. It’s very interesting and simple to design APIs in Create in Designer section in OpenAPI Specification 3.0.1. This API helps to send file from your system to target system without using Postman.
Incture Partners with Synthesized to Strengthen Enterprise Testing Capabilities
Incture has partnered with Synthesized, an AI-powered Test Data Management (TDM) leader, to enhance enterprise Quality Engineering. As organizations accelerate digital transformation, cloud migrations, and AI adoption, accessing secure test data remains a major bottleneck. This partnership enables enterprises to automatically generate secure, production-realistic test data, streamline QA automation, maintain strict compliance, and accelerate software delivery across complex IT landscapes without sacrificing quality.
Why Multiple Middleware Platforms Are Driving Up GCC Costs
Operating multiple middleware platforms inflates Global Capability Center (GCC) costs through duplicated licensing, fragmented monitoring, and severe operational inefficiencies. Platform sprawl complicates SAP S/4HANA migrations and slows down digital transformation. Consolidating legacy systems and third-party tools into a unified platform like SAP Integration Suite on BTP streamlines governance, optimizes resources, and drastically lowers total cost of ownership. Discover how to eliminate integration debt and build a future-ready GCC landscape.
