Suggestions to Improve Gamma API (Templates, Fonts, Images)
Nguyễn Trí
Hi Gamma team,
I’d like to suggest a few improvements to the API:
Add an API endpoint to GET the list of templates, so developers can dynamically retrieve and use available templates.
Add a font-family parameter to the generations API. I’m working with Vietnamese content, and many fonts currently cause accent/diacritic rendering issues, so having control over fonts would help ensure correct display.
Extend imageOptions.source to include a Stock Photos option, as this seems to be missing at the moment.
These additions would greatly improve flexibility and usability for developers working with multilingual content.
Thanks!
Nik Payne (Gamma design)
Hey Nguyễn Trí, thanks for the super thoughtful, concrete API feedback. I’m going to pass this along to the team.
Quick couple questions so we capture it right:
1) For the templates endpoint, do you need just IDs/names, or also metadata like categories, preview thumbnails, and which ones are compatible with which doc types?
2) On the Vietnamese font issue, can you share 1-2 example strings and which fonts are currently breaking diacritics for you (plus where you’re seeing it, editor vs exported output)?
3) For Stock Photos in imageOptions.source, are you imagining it should behave like “search by keyword” or more like “auto-pick a relevant stock image”?
Nguyễn Trí
Hey Nik Payne (Gamma design) , thanks for the quick follow-up!
- For templates, I’d prefer having metadata (categories, thumbnails, compatible types) to build a proper picker UI.
- For the Vietnamese font issue, I’ll attach a screenshot. It would also help if we could set font-family— fonts like: Be Vietnam Pro, Noto Sans, Inter, Roboto work well with Vietnamese diacritics.
- For imageOptions.source, I’d prefer "auto-pick a relevant stock image" based on the content.
Hope this helps!