Skip to Content
Technical Articles
Author's profile photo Rui Nogueira

SAP BTP service metadata now available on GitHub

The adoption of SAP BTP services by SAP customers and partners is steadily increasing. Many customers are utilizing SAP BTP services in their mission critical business processes.

At the same time, the speed of software development is increasing. So that means, projects on SAP BTP have to be set up fast, reliably, and in a repeatable fashion.

How can we address these challenges on SAP BTP?

Setup SAP BTP accounts & services with btp-setup-automator

With the btp-setup-automator tool developers can use an open-source tool that helps them with the automation tasks on setting-up their SAP BTP accounts and services. The btp-setup-automator was delivered in March 2022 to help developers with such setup tasks. And there is already some traction on the open-source tool: partners like e.g. Uniorg are using it to setup the SAP Business Technology Platform for their customers as you can see on their udina web-page.

One thing that is maybe not obvious to everyone using the tool today: you need to have machine-readable metadata, describing everything there is to know about resources on the SAP Business Technology Platform, to make this work. The btp-setup-automator is making use of such data from the very beginning. And as such data might be usable for other development tasks as well, SAP is exposing that data today through a new open source GitHub repository for BTP service metadata.

SAP BTP service metadata on GitHub

The GitHub repository for btp-service-metadata provides machine readable metadata about all the SAP BTP services available via an SAP BTP account with a pay-as-you-go license. All of that as an open-source project.

In order to make the data easy to digest and considering the different needs of different personas we decided to store the data in a persona-based approach starting with developers. The structure is therefore stored in a directory called v0/developer with JSON files containing service metadata, one file per service.

As an example here are some screenshots from the exposed JSON structure for the process-automation service:

In addition, the inventory list provides an overview of all available services to enable to have a quick overview what is available and what is not.

How to use machine-readable SAP BTP service metadata?

Using other tools like jq or your own code, there is a lot you can do with that data. You can for example create automatically generated human-readable pages like a documentation page per service. Need more inspiration? Checkout the metadata-exploration page from this repo on how to access and use the data.

Way forward: let us know your feedback!

Based on your feedback we will add additional personas and curated metadata. Therefore, please let us know:

  • Is the data useful to you?
  • How are you using that data and for which purpose?
  • Do you think we should have other output formats of the data?
  • Do you see wrong information in the repo?

Please engage with us on the GitHub page itself. You can raise issues or provide feature requests around the SAP BTP service metadata. You can as well start discussions on the GitHub repository to raise questions in case you have some.

Thanks a lot!


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Mauricio Lauffer
      Mauricio Lauffer

      This is great news! I was using the OData Service behind SAP Discovery Center to extract all services details and their icons. Having an official place to get this sort of information is paramount. Thanks for sharing.

      I've already updated my script to use the repo as data source. It works like a charm!

      You can see the results here:

      Create SAP BTP solution diagrams with (


      Author's profile photo Rui Nogueira
      Rui Nogueira
      Blog Post Author

      This sounds great Mauricio. And did I get it right you ALREADY!! integrated this?


      Author's profile photo Mauricio Lauffer
      Mauricio Lauffer

      That's correct, already using it for real 😋

      Author's profile photo Marco Hammel
      Marco Hammel

      Hi Rui Nogueira ,

      This is useful information to check for possible region dependencies and conflicts specifically for our customer we help to determine a multi-region, -tenant, and hyperscalers setup. It'd be even better to have the planned maintenance information for the different service-region instances as well as general SLA information about the service contracts.

      This way, you can determine account and service dependency options based on the customer's requirements.



      Author's profile photo Rui Nogueira
      Rui Nogueira
      Blog Post Author

      Thanks for your feedback Marco. We'll look into this for future versions of the repository.


      Author's profile photo DJ Adams
      DJ Adams

      Here's a quick link to the related news item from SAP Developer News this week at SAP TechEd

      Author's profile photo Rui Nogueira
      Rui Nogueira
      Blog Post Author

      Thanks DJ Adams for the cool video. Like it!

      Author's profile photo Pankaj Kumar
      Pankaj Kumar

      Hi Rui,


      Thanks a lot for the detailed blog.

      My question is - Since BTP Services gets updated randomly without the knowledge of Customer, is it possible to extract the version details of the BTP services using this BTP service metadata. Can you please throw some lights on this.