Skip to Content

Introducing SAP Cloud for Customer OData API V2

The new API – c4codataapi

With the 1808 release of SAP Cloud for Customer, SAP announced the general availability of the next version of SAP Cloud for Customer OData API – V2. The new API is based on the OData service c4codataapi and it is documented here. The c4codataapi is superior to its predecessor (c4codata) for several reasons.

Better now and in the future

At first, you will notice that the new API offers more than twice as much content compared to its predecessor – c4codata. This is because c4codataapi is a virtual service that is based on more than 40 individual OData services, altogether they expose more than a thousand entities. Thanks to its innovative technology, you can consume c4codataapi  just like another OData service. It has its own endpoint URL, metadata and service document. Similar to its predecessor, c4codataapi can also be used in OData notifications or be extended by adding custom fields – though extending c4codataapi is done via the underlying individual services.

But not all of its benefits are readily available yet. For example, its underlying technology is capable of supporting cross-navigations (i.e. associations between different objects). You will see such enhancements coming in future releases, ultimately making the new API even more versatile.

What else?

Together with the introduction of the new OData API, SAP also announced the deprecation and planned retirement of synchronous SOAP services (a.k.a. A2X) and the SAP Cloud for Customer OData API V1 – c4codata.

Deprecated APIs will continue to work and be supported until the February 2020 release of SAP Cloud for Customer. Then they will be retired – i.e. not supported. Therefore, we recommend our customers and partners to use the new OData API in their new projects. Similarly, we recommend our customers to enhance their existing interfaces based on the deprecated APIs to use the new OData API instead.

How to tell if you are using the deprecated OData API V1

Identifying if your interface is using c4codata is relatively easy. To do so, you can simply check the URLs of any SAP OData service requests within your interface and verify if it contains the pattern ‘…/odata/v1/c4codata/…‘. If it does, that means, your interface is using the deprecated OData V1 and you should plan on updating that with the new OData API (c4codataapi). (Please note that the v1 in the URL indicates the framework version and it is the same for all C4C OData services.)

Please note that the metadata of the old OData API (c4codata) and the new OData API (c4codataapi) are not equivalent. Hence, you will need to update your interface based on the metadata of the new OData API – c4codataapi.

How to tell if you are using a deprecated SOAP API

SAP Cloud for Customer provides two different types of SOAP (Web) Services as synchronous (A2X) and asynchronous (A2A).

Since not all SOAP services are deprecated, it might not be as obvious to check whether or not your interface is using an A2X SOAP service. To do so, go to the page with the list of SAP Cloud for Customer SOAP services and locate the SOAP service you are interested in. In order to see the technical name of the service, you will need to click on the link under the Service Description. Information on whether or not the service is synchronous is available in the detail page under the attribute “synchronous” with a value “yes” or “no”. Please note that if the service you are interested in is synchronous, you will need to plan reimplementing that using the respective entity-set of the new OData API – c4codataapi. The vast majority of the SOAP API usage is on the asynchronous (A2A) services. Therefore, only a small number of customers will be impacted by this change.


Best regards,


You must be Logged on to comment or reply to a post.
  • Hi Mustafa,

    thank you for this write-up. Is there a reference document to enable/implement OData API v2 – c4codataapi for cloud for service? We want to connect to an Analytics Cloud system and need to use the new standard for our OData link. Thank you!

    • Hi,

      Looks like the documentation is not very clear on this. Sorry about that. We will certainly address it ASAP.

      In the meantime, you can locate the URL for c4codataapi, via the OData Service Explorer in the Administrator work-center. To do so, just select c4codataapi and click on View. Then you will see the OData service URL, at the top of the page, under “Service URL”.

      Here is the pattern: – https://my<6-digit_tenant_id>$metadata



  • Good day Mustafa Saglam,

    Inbound Service OperationalDataProvisioningIn for ODP info extraction of info from C4C to BW will be also deprecated?  I check for this service in the link you mentioned but didn´t find it.

    Thank you and best regards,


    • Hi Monica,


      Even though it is an A2X service, this one will continue to be supported as it is specifically for BW.


      Best regards,


  • Hi Mustafa,


    Is this apply to standard A2X web services only? How about those custom A2X web services that we developed? Do we need to re-develop those with OData v2?


    Thank you.



    • Hi Edison,

      The restriction only applies to SAP provided A2X (sync-SOAP) and OData V1 services. Custom SOAP or custom OData services built by customers/partners will continue to work as before. Thus, no changes are needed on them.




  • Hi,

    Does SAP have any roadmap for building a reusable library in SAP Cloud Applications studio for parsing JSON response?

    Working with SOAP request and response is easy in ABSL with all the libraries provided. However, for Odata services, we get a response in JSON format. The structure of this response could vary for different services. It is time consuming to write a code in ABSL for parsing JSON for every web service with different response structure.

    It would be great if SAP can come up with some way to parse the JSON response in ABSL.