Custom URL, Login Removal, and Export Options for Gamma Viewer Use Cases | Gamma Community

Gamma Community Icon

Max J.
·
·
Hey Josh -- thanks for the follow-up. Let me go through each one. Custom domain for the viewer The API doesn't support this. The gammaUrl you get back always points to gamma.app and there's no way to change that. For the corporate firewall issue, the only option right now is to generate with exportAs set to "pdf" or "pptx" and host that file on your own domain. You lose the interactive viewer but it gets through the firewall. We're tracking embeddable viewer / custom domain as feedback from API users. Removing the login button Also not supported -- the viewer UI isn't configurable through the API. Same story: if you serve the exported file from your own domain, there's no Gamma UI involved at all. Multi-format export without regenerating The exportAs field only accepts a single value (pdf, pptx, or png) per generation. The Gamma itself is always created regardless -- you get a gammaUrl and gammaId back no matter what. But there's no endpoint to export an already-created Gamma into a different format after the fact. So if you need both PDF and PPTX, that requires two separate generation calls -- two credit charges, and the AI output could differ slightly between them. We've heard this from other API users and it's on our radar. Let me know if you have other questions.
Josh O.
·
·
Thanks Max J.. Really hoping you guys implement the items above. Basically means right now I cant offer a viewer and they dont get to see what Gamma can do because the output will end up being PPT as I am not going to generate it twice partly because of the tokens but also because the outputs wont match and I dont want to field questions as to why they dont match.
Max J.
·
·
That's completely fair feedback! We appreciate your interest and hope we can continue building to suit use cases like yours in the future. That being said I can't provide any details on if and when these features would be available.
Josh O.
·
·
I assume switching to the MCP doesnt solve for these right?
Max J.
·
·
Correct -- the MCP connector has the same capabilities, so those limitations would still apply there too.