Issue with Credits Deduction but No PPT Generated Using Gamma Pro API Key

·Feb 17, 2026 12:41 PM·

I am a Gamma Pro user. I used API key in an application to generate a PPT based on the inputs entered in the application frontend. The credits got used by no PPT generated on my login.

1 comment

· Sorted by Oldest

Max J.
·
·
Hey Mathangi! 👋 Thanks for reaching out. When generating via the API, the presentation won't automatically show up when you log in the way it would if you created it in the app. Instead, the link to your generated Gamma comes back through the API response itself. Here's how the flow works:
1.
You send a POST request to /v1.0/generations (or /v0.2/generations)
2.
You get back a generationId
3.
You poll GET /v1.0/generations/{generationId} until the status changes from pending to completed
4.
The completed response includes your gammaUrl (and exportUrl if you requested PDF/PPTX export)
{ "generationId": "abc123", "status": "completed", "gammaUrl": "https://gamma.app/docs/your-presentation-xyz", "credits": {"deducted": 150, "remaining": 3000} }
So if credits were deducted, your presentation was likely created successfully. The gammaUrl in that response is how you access it. If your application isn't surfacing that URL, the polling step may not be wired up correctly on the app side. To track down the specific generation, could you share: Which tool or platform is your application using to call our API? (Zapier, Make, custom code, etc.)
1.
The x-request-id from the response headers, if available
2.
A screenshot or video of your app's setup, if possible
This will help me confirm the generation went through and get you the link to your presentation. Full docs on the async flow are here: https://developers.gamma.app Let me know and I'll help sort this out!

Max J.
·
·
Hey Mathangi! 👋 Thanks for reaching out. When generating via the API, the presentation won't automatically show up when you log in the way it would if you created it in the app. Instead, the link to your generated Gamma comes back through the API response itself. Here's how the flow works:
1.
You send a POST request to /v1.0/generations (or /v0.2/generations)
2.
You get back a generationId
3.
You poll GET /v1.0/generations/{generationId} until the status changes from pending to completed
4.
The completed response includes your gammaUrl (and exportUrl if you requested PDF/PPTX export)
{ "generationId": "abc123", "status": "completed", "gammaUrl": "https://gamma.app/docs/your-presentation-xyz", "credits": {"deducted": 150, "remaining": 3000} }
So if credits were deducted, your presentation was likely created successfully. The gammaUrl in that response is how you access it. If your application isn't surfacing that URL, the polling step may not be wired up correctly on the app side. To track down the specific generation, could you share: Which tool or platform is your application using to call our API? (Zapier, Make, custom code, etc.)
1.
The x-request-id from the response headers, if available
2.
A screenshot or video of your app's setup, if possible
This will help me confirm the generation went through and get you the link to your presentation. Full docs on the async flow are here: https://developers.gamma.app Let me know and I'll help sort this out!