Zach H.

Commented on Understanding Request Prioritization and ID Usage·Posted inIdeas & Requests

Yes that would be helpful too Chowderr M..

Providing another input called callbackURL so that when the request is completed, a webhook is sent to that request.

But I disagree that a URL shouldn't be sent back. I can't think of a single scenario where I don't need a URL returned to me.

Commented on Understanding Request Prioritization and ID Usage·Posted inIdeas & Requests

Zach H.

Kinda... An ID means you still have to poll to get the URL since the URL is really what I'm looking for. A URL would mean that you don't have to poll.

Posted in Ideas & Requests·

Zach H.

Improving Gamma API Success Response with Temporary URLs

Playing around with the Gamma API and there's something that bothers me about the Success response. While I understand it doesn't yet have the final URL, it seems like it should at least have a temporary URL.

{
  "generationId": "yyyyyyyyyy"
  "tempURL": "https://gamma.app/tmp/<uuid>"
}

Why? If it had a temporary URL, then I wouldn't need to work on a system that polls gamma every few seconds. But what if someone visits the temp URL while it's still generating?

Well that should be okay! Give me the coolest 3-eyed cat "Waiting" page. When it's complete, this page will simply redirect to the generated gamma. If a user visits it again, it should 307 redirect.

1Comment

Improving Gamma API Success Response with Temporary URLs

About