Chowderr M.

I mean, I am mostly a builder and API are my specialty so I can say I might be looking at it the wrong way, but knowing how most platforms are built when you don’t get a URL on every generation, there’s a reason. I’m not sure what you’re generated with gamma but I can guarantee that every request does not send a URL and some do it’s probably because of how much can be generated instantly at one time or how small it is some of mine I don’t need to go grab and the ID at all, I already have one. Zach H. web book thing was the first thing I mentioned that Gamma should have hopefully they implement it. I’m not sure what you’re building in but if you need a different perspective, I’d be happy to give you one, but you definitely should not be just polling. That is not something you do and automations in general, it's a serious waste.

Polling is optional, when you have the ID, it can be saved somewhere. Polling in automations are actually never recommended. It would actually be better for gamma to add a web hook functionality so it can just be sent somewhere when it's finished. But the point I’m trying to make is a URL is literally not generated on every response so there’s no way that could happen at this moment. Zach H. There is no reason to continually poll and waste resources for no reason. I’m not sure how much API work you do, but that’s why most platforms don’t do that anyway .

Just the url? Got it. I also agree.

Curious on what you specifically say for links to be used when prompting.

Just want to share some information: Using something like Claude Code or an API would solve that credit issue really easily. Even with that the credit system is not a problem - just copy and pasting, not reading docs, tools, and a plethora of other reasons would "kill" vibe coding.

Just to confirm, you are trying to get a picture of what is generated? Like any picture of the entire Gamma? Jason G. Also what is the codebase of your app?

Check my latest post.