Improve API | Voters

Improve API

Alexandre Boigues

Download json parameter file (api format) from prompt source interface
AS A user, 
I WANT to download json file parameters (api format) from prompt source interface
SO THAT allows to check parameters used on user interface and API

Nik Payne (Gamma design)

Merged in a post:

Control the placement of images programmatically through API

maysam lavasani

Feature Request: Programmatic Full-Bleed / Full-Screen Image Control via API I’m using the Gamma API to generate presentations programmatically, and I need the ability to control image layout—specifically to render images as full-bleed (edge-to-edge, full-screen) slides. Currently, accent images are automatically placed and scaled by Gamma’s AI, with no API parameters to control their size, positioning, or layout. As a result, it’s not possible to reliably create image-only, full-screen slides via the API today.

Nik Payne (Gamma design)

Merged in a post:

Add POST to /themes API endpoint

Adrian Hannigan

Allow creation of themes from the API.

Nik Payne (Gamma design)

Merged in a post:

Add POST to /folders API endpoint

Adrian Hannigan

Allow creation of folders from the API.

Nik Payne (Gamma design)

Hey Adrian Hannigan, appreciate the clear ask here. I’ll pass this along to the team. Quick couple questions so we build the right thing: 1) what’s your main workflow for creating themes via API (ex: generate per customer, sync from a design system, CI step)? 2) what would the minimum POST payload need to include for you (colors, fonts, spacing, logo, anything else), and should it return a theme ID you can apply immediately to a doc/deck?

Adrian Hannigan

Nik Payne (Gamma design)
1) Yes, basically both of those, syncing data from a design system per customer
2) Ideally colors (theme palette, text, background), fonts, some level of control over design would be nice, and logo)
Yes, expected response would include a themeId that I can immediately use on the POST /generations
 endpoint

Nik Payne (Gamma design)

Hey Adrian Hannigan, love the straightforward ask here. I’ll pass this along to the team.
Quick couple questions so we build the right thing:
1) What’s your main workflow for creating folders via API (bulk import, syncing from another system, per-user setup, etc)?
2) What fields do you need on create (name only, parent folder ID, workspace/team ID, permissions), and should it be idempotent if the folder already exists?

Adrian Hannigan

Nik Payne (Gamma design)
1) per-user setup, creating a folder and then assigning the folderId on our system for future calls to /generations
2) Really just name. Looking at the UI I expect the data model would require some assignment of permissions/members, but auto assigning a sane default would be ok for our use case

Nik Payne (Gamma design)

Merged in a post:

Custom Domain Publishing

Phillip Brown

I've been creating presentations via AP through my own custom CRM which builds a around actually business proposals I also want to gather signatures which I have had to implement a sort of secondary process to get sign off for But ideally I'd like to be able to publish the site to an encoded URL such as you do now and get back that URL under a custom domain rather than the gamma dot site I'd rather keep everything under our own brand so custom domains like a generic custom domain for everything and when the site gets published it goes to a unique URL on our custom domain

Nik Payne (Gamma design)

Merged in a post:

Problema com ícones na API

Sergio Omati

Ao gerar slides sobre pessoas-chave das empresas, a IA frequentemente insere ícones que não são consistentes com o conteúdo ou com o estilo da apresentação. Pela interface, parece que isso ocorre porque os ícones sugeridos não existem na biblioteca “Ícones (clássicos)”, fazendo com que o sistema utilize um fallback com ícones pouco relacionados ao contexto. Em testes, ao utilizar a biblioteca “Ícones (moderno)”, os ícones selecionados foram significativamente mais adequados. Sugiro revisar a lógica de fallback ou priorizar automaticamente a biblioteca moderna nesses casos.

Nik Payne (Gamma design)

Thanks for the super detailed writeup (and the screenshot) Sergio Omati. That fallback behavior makes total sense as the culprit, and I’ll pass this along to the team.
Quick couple questions so we can pin it down:
1) Is this happening specifically when you generate via the API, or do you see the same mismatch when generating in the editor too?
2) When it falls back, do you want it to always prefer “Ícones (moderno)”, or only when the requested icon name is missing from “Ícones (clássicos)”?

Nik Payne (Gamma design)

Merged in a post:

Programmatically read the content of existing gammas

Brigette Rouse

One thing that's blocking a more complete pipeline: there's currently no way to programmatically read the content of existing, human-edited gammas.

The API is entirely write-focused — you can generate, export what you just generated, and look up themes/folders. But if a human has edited a gamma directly (adding original insight, annotations, recommendations), that content is locked inside the platform with no programmatic exit.

We'd love to see:

GET /v1.0/gammas
— list gammas in a workspace
GET /v1.0/gammas/{id}/content
— retrieve slide/card text content as structured JSON or markdown
Optionally: a webhook that fires on publish/save, pushing content to a URL we specify

A read API would make Gamma a proper node in an automation pipeline, not just a rendering endpoint. Would love to know if this is on the roadmap.

Nik Payne (Gamma design)

Merged in a post:

Re-Export an edited gamma.

Sam Gabrail

The exportUrl is permanently tied to the state of the presentation at generation time. The Gamma API truly has no way to re-export an edited presentation.

→