We created our own user service account in EntraID and added it to Cloudability as a normal user to enable the API Key and then logged in via frontdoor to get the API Key.
Original Message:
Sent: Mon November 03, 2025 10:33 AM
From: Marimuthu Senthilkumaran
Subject: Using API to fetch Cloudability data
Thanks Jeremy.
With the option 2 - Is it possible to create API for windows service account? With the Service Account we may have to physically login and then have to create the API right? Please suggest if there is any simple methodology. I am not advised to use Apptio Service Account or Local user account here. Thanks
------------------------------
Marimuthu Senthilkumaran
Original Message:
Sent: Sun November 02, 2025 10:30 PM
From: Jeremy Bryant
Subject: Using API to fetch Cloudability data
Hi Marimuthu,
For the majority of Cloudability APIs the best practice I have found is Option 2 which highlight as the way in the documentation, the only exception I have found is the container report API where I had to use Option 1 get the data. We are also using a service account for a pulling of data from Cloudability.
------------------------------
Regards,
Jeremy Bryant
TBM Architect
Transport for NSW
Original Message:
Sent: Thu October 30, 2025 10:39 AM
From: Marimuthu Senthilkumaran
Subject: Using API to fetch Cloudability data
Hi All,
This is somewhat connected with this post IBM Cloudability
I like to understand and advise my users on the best practice, so the question I have is - From an organization perspective, which is the recommended option to fetch cloudability data using API. We don't want to have the API specific to any user, instead we will create for a Service Account.
Option 1 - Using frontdoor open token(with Private and Public key).
Option 2 - Using Cloudability API
Please advise.
I will appreciate if you can share any documentation available from IBM Apptio on this best practice.
Thanks in Advance
------------------------------
Marimuthu Senthilkumaran
------------------------------