Released APIs and Stability Contracts in SAP S/4HANA
SAP classifies APIs by release state (C1 contract) to indicate stability. Learn what Released and Deprecated mean for CDS Views and OData services.
What Is a Released API?
SAP marks certain CDS Views, OData services, and other ABAP objects as Released. This means SAP guarantees backward compatibility — the API will not change in an incompatible way across S/4HANA releases. This is known as the C1 release contract.
Release States
| State | Meaning | Recommendation |
|---|---|---|
| Released (C1) | Stable, backward-compatible | Safe to use in custom code and integrations |
| Not Released | Internal SAP use only | May change without notice — use at your own risk |
| Deprecated | Will be removed in future | Migrate to the successor API |
Why It Matters
- Upgrade Safety — Custom code using released APIs survives SAP upgrades without rework
- S/4HANA Cloud — In the Public Cloud edition, you can only use released APIs — unreleased objects are blocked
- Integration Stability — External systems can rely on released OData services without worrying about breaking changes
How to Find Released APIs
CDSee lets you filter for released objects:
- Released CDS Views (C1)
- Browse Services (check release state in bindings)
- Browse API Hub APIs (pre-released)
Deprecation and Migration
When SAP deprecates an API, they typically provide a successor — a new released API that replaces the deprecated one. CDSee shows deprecation status and, where available, links to successor objects.