API Key for Presentation Editing and White Labeling Inquiry

Carwan R. · 2025-12-01T14:07:15.513Z

Hello Grant. We just created an api key to generate presentations. We want let our customers edit the presentations we help them generate, but when they share it with their users, it should only be viewed and white labled. Is this possible? @Grant L. bth, awesome pod with Lenny. ❤️🔥

API Key for Presentation Editing and White Labeling Inquiry | Gamma Community

4 comments

· Sorted by Oldest

Max J.
·
·
Hey! 👋 I'm Max, the API engineer here at Gamma. Great question on sharing controls. Let me walk through what's possible right now. Sharing permissions - yes, you can control this When you generate via the API, use the sharingOptions parameter to set different access levels: json
"sharingOptions": { "workspaceAccess": "edit", "externalAccess": "view" }
This lets workspace members edit while external viewers only get view access. You can also use emailOptions to share directly with specific people at specific access levels. White labeling - not currently available There's no white label option in Gamma right now. Generated presentations will still live on gamma.app and carry Gamma branding. Workaround: Export If you need to remove the Gamma platform entirely, you can use "exportAs": "pdf" or "exportAs": "pptx" in your API call. This gives you a downloadable file your customers can share however they want. No Gamma branding, no gamma.app URL. The tradeoff is they lose the interactive web experience. One note on editing: The API is create-only at the moment. Your customers would need to hop into gamma.app to make any edits after generation. Can't edit existing Gammas via API yet. Here's the full sharingOptions documentation: https://developers.gamma.app Let me know if you have questions on any of this!
💡1
Carwan R.
·
·
Hey Max, thanks for the answer. API is then not really mature to solve our needs. Q:
1.
When can we access white labeling?
2.
When can we let our customers edit generated presentations inside our product?
Solution no. 2 is quite important. Otherwise, API is not useful for us.
Max J.
·
·
Hey Carwan, totally understand where you're coming from. These are both common requests we're hearing. Honest answer on both: I don't have timelines to share. Our API just moved to GA (v1.0) about a month ago after being in beta since July, so we're still in the phase of gathering feedback and prioritizing what comes next. White labeling - This is on the radar as something people want, but I can't promise when or if it'll happen. It's a bigger lift than it might seem. Embedded editing - Same story. Right now the only way to edit is in gamma.app directly. An embedded editor or editing API would be a significant new capability. What I'd genuinely recommend: Drop your use case and requirements in our feedback form. The product team actually reads these, and specific use cases like "we need customers to edit without leaving our platform" carry weight when they're prioritizing roadmap. https://developers.gamma.app/docs/get-help For now, the workarounds are what I mentioned: export to PDF/PPTX for a brandless deliverable, or have customers click through to gamma.app for editing. I know neither is ideal for what you're building. If the API doesn't fit your current needs, no hard feelings. Happy to help if things evolve or if you find a workaround that works for your use case.
Carwan R.
·
·
Thanks for the reply. We don't have issues with gamma brand at all. Just the control to who can edit and who can view.

Max J.
·
·
Hey! 👋 I'm Max, the API engineer here at Gamma. Great question on sharing controls. Let me walk through what's possible right now. Sharing permissions - yes, you can control this When you generate via the API, use the sharingOptions parameter to set different access levels: json
"sharingOptions": { "workspaceAccess": "edit", "externalAccess": "view" }
This lets workspace members edit while external viewers only get view access. You can also use emailOptions to share directly with specific people at specific access levels. White labeling - not currently available There's no white label option in Gamma right now. Generated presentations will still live on gamma.app and carry Gamma branding. Workaround: Export If you need to remove the Gamma platform entirely, you can use "exportAs": "pdf" or "exportAs": "pptx" in your API call. This gives you a downloadable file your customers can share however they want. No Gamma branding, no gamma.app URL. The tradeoff is they lose the interactive web experience. One note on editing: The API is create-only at the moment. Your customers would need to hop into gamma.app to make any edits after generation. Can't edit existing Gammas via API yet. Here's the full sharingOptions documentation: https://developers.gamma.app Let me know if you have questions on any of this!
💡1
Carwan R.
·
·
Hey Max, thanks for the answer. API is then not really mature to solve our needs. Q:
1.
When can we access white labeling?
2.
When can we let our customers edit generated presentations inside our product?
Solution no. 2 is quite important. Otherwise, API is not useful for us.
Max J.
·
·
Hey Carwan, totally understand where you're coming from. These are both common requests we're hearing. Honest answer on both: I don't have timelines to share. Our API just moved to GA (v1.0) about a month ago after being in beta since July, so we're still in the phase of gathering feedback and prioritizing what comes next. White labeling - This is on the radar as something people want, but I can't promise when or if it'll happen. It's a bigger lift than it might seem. Embedded editing - Same story. Right now the only way to edit is in gamma.app directly. An embedded editor or editing API would be a significant new capability. What I'd genuinely recommend: Drop your use case and requirements in our feedback form. The product team actually reads these, and specific use cases like "we need customers to edit without leaving our platform" carry weight when they're prioritizing roadmap. https://developers.gamma.app/docs/get-help For now, the workarounds are what I mentioned: export to PDF/PPTX for a brandless deliverable, or have customers click through to gamma.app for editing. I know neither is ideal for what you're building. If the API doesn't fit your current needs, no hard feelings. Happy to help if things evolve or if you find a workaround that works for your use case.
Carwan R.
·
·
Thanks for the reply. We don't have issues with gamma brand at all. Just the control to who can edit and who can view.