SAP APIs to test against, without fighting SAP authentication.
SAP BAH Sandbox runs on your own machine. Import an API specification from the Business Accelerator Hub and you get a mock that answers like the real service, OData included — point your product or your iFlow at it. It also keeps an eye on the Hub catalog and tells you when an API or artifact publishes a new version.
No Docker, no SAP credentials needed · MIT license · updates itself
Everything you need to test against SAP APIs
One small server with one SQLite file: mocks, change tracking, tests and a traffic log.
Mocks that answer like SAP
Import an OpenAPI 3, Swagger 2 or OData EDMX specification and mount it. Collections, key predicates, $filter, $select, $orderby, $top, $skip and the right V2 or V4 envelope — with data from a generator, your own fixtures, a local AI, or a proxied real backend.
Know when an API changes
It crawls the Hub catalog — about 1,950 packages and 42,000 artifacts, no login needed — keeps every version, and writes a report of what is new, changed or removed, with breaking changes flagged. HTML, JSON and CSV.
A test suite written for you
One test per operation, filled from the specification, checking the status code and validating the response against its schema. Read-only mode for real tenants, and an exit code for your pipeline.
See exactly what your iFlow sent
Every call to a mock is logged with headers, bodies and timing, streamed live like the browser's developer tools — malformed JSON included, byte for byte.
The unhappy paths too
Give any mock extra latency and an error rate, and exercise the retry and exception branches of your integration instead of only the happy path.
Installs and updates itself
One command installs it with its own private Node runtime and starts it at login. New releases install themselves when the sandbox is idle; your data and settings stay.
Running in five minutes
Nothing to install on SAP's side, and no account to create.
- Install itUnpack the latest release and run the installer for your system. It downloads its own Node runtime, generates an admin key and starts the sandbox.
- Import a specification and mount itDownload a spec from api.sap.com, or save a tenant's
$metadata, import it in the Mocks tab and press mount. It is live at/mock/<slug>. - Point your product or your iFlow at itCall
http://<host>:8080/mock/<slug>. For a Cloud Foundry Integration Suite tenant, the repository explains how to reach it through Cloud Connector, a tunnel or nginx.
From the command line
# Windows (PowerShell), inside the unpacked release powershell -ExecutionPolicy Bypass -File .\install\install.ps1 # macOS / Linux ./install/install.sh # then sapbah open # the UI in your browser sapbah sync --filter SuccessFactors # what changed on the Hub sapbah test --mock s4-bp --read-only # run the generated suite sapbah update --check # is there a new release?
The installer registers autostart: Task Scheduler on Windows, launchd on macOS, systemd on Linux. There is also a system-wide install for a shared team server.
Your data stays on your machine
A sandbox that sees your integration traffic has to be careful with it.
Local by design
Specifications, datasets and the traffic log live in one SQLite file on your machine. Nothing goes anywhere unless you set up a proxy mock.
A locked admin API
The installer generates an admin key. Requests another website tries to send from your browser are refused, and mock responses can never run code in the admin page.
Secrets kept out of the log
Authorization, Cookie and API key headers are redacted before anything is stored. Hub credentials are optional: the catalog is public.
No telemetry
The only outgoing request of its own is an anonymous check for a new release on GitHub, and one setting turns it off.
Free and open source, and it will stay that way
SAP BAH Sandbox is released under the MIT license: use it at work, change it, share it. If it saved you an afternoon, a small donation helps keep it going.
Questions
Do I need SAP credentials?
No. Catalog tracking uses the Hub's public catalog, and mocks work from any specification you import. Only downloading specifications automatically needs a Hub API key or a logged-in session.
Can SAP Integration Suite call the mocks?
Yes. A Cloud Foundry tenant cannot reach a private address, so use SAP Cloud Connector, a Cloudflare Tunnel or nginx — the repository has a working configuration for each.
Which specifications work?
OpenAPI 3, Swagger 2 and OData EDMX, including a $metadata document saved from a tenant. The OData engine covers the query options integrations actually send.
How does the automatic update work?
Every six hours the sandbox asks GitHub for the latest release. When there is a newer one it installs it as soon as it has been idle for 15 minutes, keeping your data and settings. You can also press Update now, or turn it off with AUTO_UPDATE=false.
Does it run on macOS and Linux?
Yes. The same installer covers both and registers a launchd agent or a systemd user service. For a server the whole team uses, there is a system-wide systemd install.
Is it an SAP product?
No. It is an independent open-source project, not affiliated with SAP. It only reads the Hub's public catalog and the specifications you give it.