# Exportable Jobs Data

**URL:** <https://community.holistics.io/t/exportable-jobs-data/2323>\
**Category:** Feature Suggestions\
**Created:** [December 10, 2024, 2:18pm UTC](https://community.holistics.io/t/exportable-jobs-data/2323 "2024-12-10T14:18:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![datbth](https://community.holistics.io/user_avatar/community.holistics.io/datbth/32/1414_2.png) [@datbth](https://community.holistics.io/u/datbth)\
**Post date:** [December 11, 2024, 3:46am UTC](https://community.holistics.io/t/exportable-jobs-data/2323/2 "2024-12-11T03:46:29Z")

</div>

Hi Bob,

Thank you for the post.

I get the idea but I’m not sure I understand the details.  
Could you please elaborate on the API details? Would an API like this be enough for your needs?

- Input
  - `source_type` (e.g. `'Dashboard'`)
  - `source_id`

- Output
  - List of jobs of the input source. Each job containing
    - Job Queue
    - Action

Besides, while having some APIs is indeed a valid and robust solution, what do you think about this solution of having a built-in dashboard for Data Warehouse Cost Analysis: [Data Warehouse Cost Analysis for Holistics Jobs](https://community2.holistics.io/t/data-warehouse-cost-analysis-for-holistics-jobs/1858)?

---

_[View the full topic](https://community.holistics.io/t/exportable-jobs-data/2323)._