What we do
Tools
Industries
Department
How we workLet's talk →
Home/SAP/SAP APIs
SAP

SAP APIs: Which Ones Your SAP System Actually Exposes

"SAP APIs" means different things depending on which SAP you run. S/4HANA exposes OData services listed on SAP's Business Accelerator Hub. ECC mostly talks through BAPIs called over RFC, and IDocs for documents like orders and invoices. Find your system below, then the steps to reach it from outside.

Your SAP system, and the interface it gives you

If you run You build against What to check first
S/4HANA Cloud, public edition Released OData (V2 and V4) and SOAP APIs from the Business Accelerator Hub, switched on through communication arrangements. Only released APIs are allowed. If the one you need isn't released for your edition, there's no back door to a BAPI.
S/4HANA on-premise or private cloud The same OData services, activated in SAP Gateway, plus BAPIs and IDocs, which still work. Whether the service is activated on your system and your release is the version the Hub page describes.
ECC 6.0 BAPIs and RFC function modules, called with SAP's Java or .NET connectors, and IDocs over ALE for orders, deliveries and invoices. Whether Gateway is installed. If not, there's no OData at all, and an outside system needs a layer in front.
SuccessFactors, Ariba, Concur and other SAP cloud products Their own APIs, also listed on the Business Accelerator Hub. These aren't S/4HANA APIs and have separate auth. Treat each product as its own integration.

From the Hub to a first working call

  1. 1

    Find the API on the Business Accelerator Hub

    api.sap.com S/4HANA Cloud or S/4HANA APIs

    Search by business object (sales order, business partner, material stock). The page lists the entity sets, fields and the communication scenario it belongs to.

  2. 2

    Try it in the sandbox

    Sign in and use Show API Key on the API's reference page, then call the sandbox with that key in an APIKey header. You see real response shapes before touching your own system.

    Watch for: the sandbox is SAP's sample data. Your system's custom fields won't be there.

  3. 3

    Open it up on your own system

    On S/4HANA Cloud, create a communication system, a communication user and a communication arrangement for the API's scenario (for example SAP_COM_0008 for business partners). On-premise, activate the OData service in Gateway (/IWFND/MAINT_SERVICE for V2) and give the technical user only the roles the job needs.

  4. 4

    Reach it from outside the network

    For an on-premise system, SAP Cloud Connector lets SAP BTP reach SAP without opening it to the internet. Without BTP, the usual route is a reverse proxy or API gateway your IT team already runs.

Where SAP API builds go wrong

A BAPI that returns success and saves nothing

How you'll know: The call comes back clean, but the sales order or goods movement isn't there.

Fix: Most BAPIs don't commit on their own. Call BAPI_TRANSACTION_COMMIT in the same RFC session, and check the RETURN table for errors even when the call itself didn't fail.

OData writes rejected with 403

How you'll know: GETs work, but every POST or PATCH fails.

Fix: SAP Gateway expects a CSRF token. Send a GET with X-CSRF-Token: Fetch, keep the token and session cookies, and send both with the write.

IDocs stuck in error status

How you'll know: Orders the other system sent never appear, and the IDoc list (WE02) shows status 51, application document not posted.

Fix: Usually master data: a material, customer or partner function that doesn't exist on the SAP side. Monitor for status 51 and send each one to whoever owns that data, rather than finding them at month end.

Building on the Hub page, not your release

How you'll know: Fields or entities in the docs are missing from your system.

Fix: Check the API's version against your S/4HANA release before writing the mapping. Older releases often carry an earlier version of the same service.

Still on ECC: build on BAPIs now, or wait for S/4HANA?

Build now

When the business needs the data this year

  • A storefront, CRM or 3PL needs live SAP data and the S/4HANA date keeps moving.
  • Put a small REST service in front of the BAPIs, so outside systems only ever see your own API.
  • When SAP moves to S/4HANA, only that service changes underneath; the other systems don't.
Wait

When the move is close and fixed

  • The S/4HANA cutover is booked and months away, not years.
  • The released OData API for the job already exists for your target edition.
  • A manual export can cover the gap without real cost.

ECC mainstream maintenance ends at the end of 2027, with paid extended maintenance to the end of 2030. That's why the wrapper approach matters: it lets you connect now without building the same integration twice.

What n-frames builds on SAP APIs

The common job is getting SAP data to the tool your team already works in, live rather than by emailed report: order status for a customer portal, account data for the CRM, and stock levels for a storefront or 3PL, which our SAP inventory page covers in depth. On ECC that usually means the REST service in front of the BAPIs described above; on S/4HANA it means the released OData APIs with proper retries and error routing.

When the other system has no API, n-frames automates its screens instead, so the SAP side still connects end to end. Choosing between direct API work and SAP's own middleware is covered on SAP Integration Suite, and matching SAP postings against bank and subledger data on SAP reconciliation.

Let's talk

Not sure your SAP system has the API the docs describe?

n-frames checks what your release actually exposes, then builds the integration on it: released OData on S/4HANA, or a REST layer over BAPIs and IDocs on ECC that survives the move to S/4HANA.

Map our SAP interfaces →

Questions people ask

Does SAP have an API?

Yes, several, and which one you get depends on the system. S/4HANA exposes OData and SOAP APIs listed on the Business Accelerator Hub. ECC relies mostly on BAPIs and RFC function modules, plus IDocs for document exchange. SAP's cloud products such as SuccessFactors and Ariba have their own.

What is the SAP API Business Hub?

It's SAP's public catalog of APIs across its products, now called the SAP Business Accelerator Hub, at api.sap.com. Each API has its documentation and a sandbox you can call with an API key, so you can see what's exposed before committing to a build.

Do I need a developer to use SAP's API?

For anything past a test call, yes. Setting up communication arrangements or Gateway services, handling CSRF tokens and BAPI commits, and mapping SAP fields to another system is development work. n-frames does that part, alongside your SAP admin.

What's the difference between SAP's API and SAP Integration Suite?

SAP's APIs are direct access to data and business objects in SAP. Integration Suite is a separate SAP middleware product on BTP for building and running integration flows, which often call those same APIs underneath. You can build against SAP's APIs directly without licensing Integration Suite.

Can I get SAP data into a system that has no API of its own?

Yes. The SAP side uses OData or BAPIs as usual, and the other side is automated through its own screens, logging in and entering data the way a person would.

Are BAPIs still supported in S/4HANA?

On S/4HANA on-premise and private cloud, yes, many still work and are widely used. On the public cloud edition, only released APIs are allowed, so plan new builds around OData there.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.