Managing Gamma Directories and Fetching Created Content via API at Scale

·Sep 16, 2025 04:44 AM·

@here just wanted to understand how you all are managing the directories in gamma, my usecase is I am generating program<> course level content and then sending it for generation using gamma using API's and I am talking this at scale, everything works fine for me but where I am struggling is:

1.
Folderwise assets presence : As each subjects have it's own modules, topics and subtopics the quantum becomes much more when everything is created without a subfolder being present
2.
Have we also introduced the fetch response from gamma after the gammas have been created using API, as in can I fetch all the gammas that I have created using API's?

6 comments

· Sorted by Oldest

Max J.
·
·
Hi there! I'm Max from the Gamma team. Directory Management: The current API doesn't support organizing Gammas into folders programmatically. You're right that this gets messy at scale. Fetching Created Gammas: No LIST endpoint exists yet - you can only retrieve individual Gammas by generationId. Current endpoints: - POST /v0.2/generations (create) - GET /v0.2/generations/{generationId} (retrieve specific) Unfortunately there aren't good workarounds for either of these limitations right now. The API parameters available (like sharingOptions) don't address the organizational challenges you're facing. Your use case is helpful feedback: Educational content generation at scale shows how these organizational features could be valuable for API users. Would be helpful to know: - How many generations you're creating per subject/module? - What your ideal folder structure looks like? (Program > Course > Module > Topic?) If you have time for a quick Loom showing your workflow, that would be gold for our product team - but totally understand if you're swamped. Thanks for building with our API!
Aarush M.
·
·
Thanks for your response but just to give you a breif numbers on an average 2000 subjects (40 campus across 3-5 programs) average of 5 modules with an average of 4 topics in each module and then double it bcz of two types of assets in each topic so if things works well as per planned we are talking about 80k successful generations every 6 months as there is definitely a syllabus change every year for each universities.
Aarush M.
·
·
We are trying it out rigorously if poc is successful we are not much far to connect over a call for better communication
Max J.
·
·
We really appreciate your enthusiasm and are genuinely impressed by the scale of your ambitions with this workflow and POC. 80k generations every six months across 40 campuses - that's the kind of transformative educational content automation that gets us excited. We have immediate plans to continue building up the capability of the API, but we can't provide exact details as things continue to develop and evolve. We appreciate you as a developer and want to see you grow and succeed with what you're building. Your presence in our community and the feedback you're sharing is really valuable to us. Stay tuned - there's more coming.
Aarush M.
·
·
Hi Max J. do we have any solution on this till date or any expected timeline?
Max J.
·
·
Aarush I appreciate you checking in! While I wish I had more specifics to share look out for announcements from me in the API Discussion channel or check our API's change log for further details about updates to our API.

Max J.
·
·
Hi there! I'm Max from the Gamma team. Directory Management: The current API doesn't support organizing Gammas into folders programmatically. You're right that this gets messy at scale. Fetching Created Gammas: No LIST endpoint exists yet - you can only retrieve individual Gammas by generationId. Current endpoints: - POST /v0.2/generations (create) - GET /v0.2/generations/{generationId} (retrieve specific) Unfortunately there aren't good workarounds for either of these limitations right now. The API parameters available (like sharingOptions) don't address the organizational challenges you're facing. Your use case is helpful feedback: Educational content generation at scale shows how these organizational features could be valuable for API users. Would be helpful to know: - How many generations you're creating per subject/module? - What your ideal folder structure looks like? (Program > Course > Module > Topic?) If you have time for a quick Loom showing your workflow, that would be gold for our product team - but totally understand if you're swamped. Thanks for building with our API!
Aarush M.
·
·
Thanks for your response but just to give you a breif numbers on an average 2000 subjects (40 campus across 3-5 programs) average of 5 modules with an average of 4 topics in each module and then double it bcz of two types of assets in each topic so if things works well as per planned we are talking about 80k successful generations every 6 months as there is definitely a syllabus change every year for each universities.
Aarush M.
·
·
We are trying it out rigorously if poc is successful we are not much far to connect over a call for better communication
Max J.
·
·
We really appreciate your enthusiasm and are genuinely impressed by the scale of your ambitions with this workflow and POC. 80k generations every six months across 40 campuses - that's the kind of transformative educational content automation that gets us excited. We have immediate plans to continue building up the capability of the API, but we can't provide exact details as things continue to develop and evolve. We appreciate you as a developer and want to see you grow and succeed with what you're building. Your presence in our community and the feedback you're sharing is really valuable to us. Stay tuned - there's more coming.
Aarush M.
·
·
Hi Max J. do we have any solution on this till date or any expected timeline?
Max J.
·
·
Aarush I appreciate you checking in! While I wish I had more specifics to share look out for announcements from me in the API Discussion channel or check our API's change log for further details about updates to our API.