Wondering when webhooks will be added instead of polling for 5-10 (etc)? Max J.
Hey Chowderr M.! Webhooks could definitely make life easier than polling in certain use cases. For anyone following along: webhooks would let you give us a URL that we'd hit automatically when your generation completes, instead of having to check every 30 seconds. Much cleaner for automation. I don't have any updates on if/when we might add webhook support, but I can see how it would improve your workflow. The polling pattern works but it's definitely not ideal for production integrations. What are you building that's making the polling feel particularly painful?
I would not say it's painful. I am just familiar with platforms allowing us to add a webhook instead of polling. For now I will just run a cron to pull the ID from a table and fetch. I was just curious as I thought I saw somewhere the links could expire? This is another project I help manage that you can use as a reference: https://github.com/stephengpope/no-code-architects-toolkit - we allow users to add a webhook so we can send that information wherever as some request may take a few minutes depending on whatever it is. I am building a micro-saas/SaaS framework for this already and already have created a Gamma MCP that I will be sharing.
Your cron approach sounds like a good solution for the polling piece. Regarding the URLs: based on the GET endpoint behavior, the gammaUrl returned should stay consistent, so your table-based workflow should work fine for tracking and fetching those. The SaaS framework and MCP project you're working on look really interesting! That kind of backend development is outside my scope since I focus specifically on the Gamma API integration piece. But if you have any questions about the API requests, response formatting, or parameters while building that out, feel free to reach out. Looks like you have a solid plan in place!
No problem, I will reach out anytime. I plan to share it with everyone. I have takes notes and added to documentation as well. My specialty is API's for 16 years now. I love connecting things together. Question: the limit for request is still 50? If so when will this ramped up? That is really my main question.
Nice that you're documenting as you build. That kind of documentation work is always helpful. 16 years of API work, that's solid experience! You definitely know your way around integrations. On the 50 generation limit: very soon we'll be ramping that up but I can't say exactly when just yet. I know it's probably the main constraint for automation workflows right now. Looking forward to seeing what you build with the MCP and SaaS framework.
Thank you. I hope its soon. Question: For "exportAs" we can use multiple options? So it would be: (added an example) curl --request POST \ --url https://public-api.gamma.app/v0.2/generations \ --header 'Content-Type: application/json' \ --header 'X-API-KEY: ilovegamma' \ --header 'accept: application/json' \ --data ' { "inputText": "Example text", "exportAs": "pdf, pptx", "sharingOptions": { "externalAccess": "view", "workspaceAccess": "noAccess" }, "imageOptions": { "source": "aiGenerated", "model": "flux-1-quick", "style": "minimal lineart style illustration with a hearts" }, "additionalInstructions": "Make the titles catchy", "cardSplit": "auto", "numCards": 3, "format": "presentation", "textMode": "generate" } ' Also will there be a page for all of the themes for Gamma?
I have it already. I can share it now or after I do the build. Up to you. (Regardless it will be shared) I just have testing to do. I will have to test it but I am curious if we send the same request and then just change pdf to pptx and it will be exactly the same? Or we can expect a change? Which leads me into the next question: Will we have an endpoint to update an existing Gamma through API? I am sure that will take some time but curious if you guys are thinking about that.
excuse me yes you can access all themes by going to https://gamma.app/#themes and selecting "Standard"