Include “Tag” Field in the Cost Explorer API Response
We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint:
https://cloud.mongodb.com/api/atlas/v2/orgs/%s/billing/costExplorer/usage
Background
Our team generates detailed monthly reports on departmental usage costs using the API. Each month, we provide information such as:
• Organization ID
• Project ID
• Cluster Name
To categorize costs, we use tags to assign each cluster to specific internal department categories. These tags are already included in the CSV file available at billing > invoices > download > csv, allowing us to categorize costs accurately.
Challenge
While the current CSV file approach works, it requires downloading, parsing, and managing files, which introduces unnecessary complexity and file management overhead. Including the tag field directly in the API response would allow us to streamline this process and avoid handling files entirely.
Request
We kindly request the addition of a “tag” field in the response of the API endpoint mentioned above. This enhancement will enable us to:
1. Automate our cost categorization and reporting process.
2. Eliminate the need for manual file parsing and management.
3. We can calculate costs by department or application and use resources more efficiently.
Myungho
shared this idea
-
Gyuhern
commented
I completely agree. Adding a tag field to the API response would significantly improve workflow efficiency. The manual process of downloading and parsing CSV files is both time-consuming and prone to errors, especially for repetitive tasks. Having tag information available directly through the API would make automation much simpler and greatly enhance resource allocation. I really hope this gets implemented!