Is it allowed to use Gamma API for generating presentations in my app under the current terms of service?

·Mar 23, 2026 04:04 PM·

Have an API usage question. I'm building an app where one of the output options is a presentation. I'd love to use Gamma instead of PPT. I just want to make sure I am not violating terms of service. I read the terms (https://gamma.app/terms) specific to the API and I just want to make sure I am good. General idea is my platform generates content for the user based on their inputs. The output options are word doc, PDF, or Presentation. The content would (ideally) get sent to Gamma and the presentation would get generated and returned back (probably as a link for them to then download it). I'd be consuming credits for the generation of the deck via the API. Is that okay? If not my workaround is to build it in a PPT template but I'd LOVE to use Gamma if I can.

👀1

2 comments

· Sorted by Oldest

Josh O.
·
·
I should add - the app is specific to a single type of user and usecase, it's not general topics / any kind of output or preso. Happy to show more if someone needs to understand more than I have put here.
Max J.
·
·
Hey Josh! Love this use case — it's exactly the kind of thing the API was built for. Short answer: you're good. We have multiple companies doing this exact pattern today — platforms that call Gamma's API on the backend to generate presentations for their end users, with the platform owner consuming credits. It's a core use case, not an edge case. The ToS (Section 1.2a) explicitly grants a license to use the API to "develop, maintain and support any software application you developed... under your branding" and to "display your Applications to the appropriate end users." So your model of platform generates content, sends to Gamma, returns a link or file to the user — that's squarely within bounds. A few things on the technical side that might help: The flow is straightforward. POST /v1.0/generations with format: "presentation" and your content as inputText. Set exportAs: "pptx" if you want a downloadable PowerPoint file — when the generation completes, you'll get an exportUrl your users can download from. You also get a gammaUrl if they want to view/edit on gamma.app.
1.
Credits deduct from your API key's workspace, which is the expected model. You can check credits.remaining in the poll response to track your balance.
2.
One callout — if your app collects personal info from end users, you'll need a privacy policy that discloses Gamma's involvement (Section 1.2b). Standard for any app using third-party APIs.
3.
What the API doesn't do today — you can't edit an existing Gamma after creation via the API, so each generation is a fresh deck. If users want to tweak the output, they'd do that on gamma.app directly.
Definitely go with Gamma over the PPT template route — the output quality will be night and day. Let me know if you have questions on the implementation side!

Is it allowed to use Gamma API for generating presentations in my app under the current terms of service? | Gamma Community

Josh O.
·
·
I should add - the app is specific to a single type of user and usecase, it's not general topics / any kind of output or preso. Happy to show more if someone needs to understand more than I have put here.
Max J.
·
·
Hey Josh! Love this use case — it's exactly the kind of thing the API was built for. Short answer: you're good. We have multiple companies doing this exact pattern today — platforms that call Gamma's API on the backend to generate presentations for their end users, with the platform owner consuming credits. It's a core use case, not an edge case. The ToS (Section 1.2a) explicitly grants a license to use the API to "develop, maintain and support any software application you developed... under your branding" and to "display your Applications to the appropriate end users." So your model of platform generates content, sends to Gamma, returns a link or file to the user — that's squarely within bounds. A few things on the technical side that might help: The flow is straightforward. POST /v1.0/generations with format: "presentation" and your content as inputText. Set exportAs: "pptx" if you want a downloadable PowerPoint file — when the generation completes, you'll get an exportUrl your users can download from. You also get a gammaUrl if they want to view/edit on gamma.app.
1.
Credits deduct from your API key's workspace, which is the expected model. You can check credits.remaining in the poll response to track your balance.
2.
One callout — if your app collects personal info from end users, you'll need a privacy policy that discloses Gamma's involvement (Section 1.2b). Standard for any app using third-party APIs.
3.
What the API doesn't do today — you can't edit an existing Gamma after creation via the API, so each generation is a fresh deck. If users want to tweak the output, they'd do that on gamma.app directly.
Definitely go with Gamma over the PPT template route — the output quality will be night and day. Let me know if you have questions on the implementation side!