# Is it possible to get the "folders" in job path?

**URL:** <https://matillioncommunity.discourse.group/t/is-it-possible-to-get-the-folders-in-job-path/1765>\
**Category:** Matillion ETL\
**Created:** [May 30, 2022, 4:00pm UTC](https://matillioncommunity.discourse.group/t/is-it-possible-to-get-the-folders-in-job-path/1765 "2022-05-30T16:00:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![LMenz](https://avatars.discourse-cdn.com/v4/letter/l/a5b964/32.png) [@LMenz](https://matillioncommunity.discourse.group/u/LMenz)\
**Post date:** [May 30, 2022, 4:00pm UTC](https://matillioncommunity.discourse.group/t/is-it-possible-to-get-the-folders-in-job-path/1765/1 "2022-05-30T16:00:53Z")

</div>

I'm trying to get a list of our jobs (transformations and orchestrations) for use in a tool that I'm going to be working on and I was looking at the MetaData API - but the URLs which show in there just have project/environment/job\_name while in the UI we have them arranged in folders (sometimes a few levels deep).

&nbsp;

Looking at the UI, I can see that the URLs there don't actually show the folders either but they do exist so something, somewhere, must know about them!

&nbsp;

Can anyone give me any pointers as to how I might go about getting a list of jobs organised into their folders?

---

<div class="post-metadata">

**Author:** ![Bryan](https://avatars.discourse-cdn.com/v4/letter/b/db5fbb/32.png) [@Bryan](https://matillioncommunity.discourse.group/u/Bryan)\
**Post date:** [June 6, 2022, 9:17pm UTC](https://matillioncommunity.discourse.group/t/is-it-possible-to-get-the-folders-in-job-path/1765/2 "2022-06-06T21:17:42Z")

</div>

Hi [@LMenz](https://matillioncommunity.discourse.group/u/LMenz)​,

In looking at the documentation and experimenting a bit with the API, the only way to get this is to export the project. Since a given project can have 1 to n versions I would focus on one that you know will always be there. For example we have a version called CURRENT in all of our projects which is the version we use in all schedules and is considered the "released" version. In this scenario I would export the specific version of the project. The response is going to be quite large but it sounds like you will only need to focus on a couple of attributes. Those attributes being things like Job Name, Job Type, and Job Path. For those items below is their respective paths in the JSON:

/objects/jobs/objects/info/name

/objects/jobs/objects/info/type

/objects/jobs/objects/path

Path is what you are likely going to be interested in. Path is an array of names. For example, if a job were in the following path, "Archive/Old/Jobs" the Paths array in the JSON will be Archive, Old, Jobs.

I hope this helps! Post back if you need more help.