Gregory L.

Hi Gamma team, I am running into an issue using templates with the API. In short, I've created a template, and I need to ensure that I am sending the verbatim text forward for the presentation that I'm creating. All of the research points to the fact that "preserve text" is not an option that can be used with the template's endpoint. Is there any workaround for this? The actual verbatim text that is being pushed forward is absolutely critical. So, as a little bit more context, I ended up going down the templates path due to the 5,000-character limit associated with additional instructions, which I was using to define and describe each of the slides.

Feature Request: Folder and Subfolder Support via Gamma API I’d like to request the ability to create folders via the Gamma API. In addition, it would be very helpful to introduce support for subfolders, allowing for a hierarchical folder structure. This would enable more structured organization directly through the API and improve overall workspace management.

Feature Request: Clickable Hyperlink Support in inputText (preserve mode) We are using the Gamma API to generate professional research documents for investors. Our workflow assembles a large body of market research content - sourced from live web research - and sends it to Gamma via the generations endpoint using textMode: "preserve". At the end of every document we include a Sources section that lists the citations used throughout the document. Each citation has a label (e.g. [1.1], [4.3]) and a source URL. We want readers to be able to click those URLs to open the source in a browser. What we tried: - Standard markdown link syntax: [1.1](https://source-url.com) - Gamma renders this as literal text, not a clickable link. - Bare URL: https://source-url.com - not auto-linked. - After reviewing the full developer documentation at developers.gamma.app, we found no documented syntax for creating clickable hyperlinks within inputText. What we are asking for: A supported way to include clickable hyperlinks in inputText content when using textMode: "preserve". This could be standard markdown link syntax [text](url), bare URL auto-linking, or a Gamma-specific encoding - whatever fits the platform's architecture. A secondary related request: per-card textMode control, so that specific cards (such as a References card) could use textMode: "generate" while the rest of the document uses textMode: "preserve". This would allow Gamma's own rendering to handle links on those cards. Why it matters: Source citations are a credibility requirement in professional research documents. Without clickable links, readers must manually copy and paste each URL - which is a significant friction point in a document designed to build investor confidence.

Hi Gamma Team, One request here is the ability to get granular detail on where, how, and when my API credits are being consumed. This arose because I think I am running into a very large discrepancy in the number of credits I have available to me, and I have no way to trace it back. As an FYI, I've been working with Support Sale, and we'll see what's going on here.