Google Gemini Ditches Polling for Webhooks on Long Jobs

May 6, 2026

Google Gemini Ditches Polling for Webhooks on Long Jobs

Published: May 6, 2026 at 12:15 AM

Updated: May 6, 2026 at 12:15 AM

100-word summary

Google just rolled out webhooks for Gemini API, letting developers skip the constant "are we there yet?" polling for batch jobs and video generation that can run for hours. Instead of checking back every few seconds, your app gets pinged the moment work finishes. The system retries failed deliveries for 24 hours and blocks stale notifications older than five minutes to prevent replay attacks. You can set a default webhook for your entire project or point specific jobs to custom endpoints. The catch: webhooks only send a thin notification, not the actual result, so you still need to fetch the output yourself. No more wasting API calls asking if your...

What happened

Google just rolled out webhooks for Gemini API, letting developers skip the constant "are we there yet?" polling for batch jobs and video generation that can run for hours. Instead of checking back every few seconds, your app gets pinged the moment work finishes. The system retries failed deliveries for 24 hours and blocks stale notifications older than five minutes to prevent replay attacks. You can set a default webhook for your entire project or point specific jobs to custom endpoints. The catch: webhooks only send a thin notification, not the actual result, so you still need to fetch the output yourself.

Why it matters

No more wasting API calls asking if your video render is done.

Sources