Gemini API Introduces Webhooks for Long-Running Tasks
Key point
Gemini API has introduced Webhooks for long-running tasks, eliminating the need for polling.
Details
Gemini API has introduced event-driven Webhooks to reduce the repeated polling required to check the status of long-running tasks. As soon as a task finishes, it sends an HTTP POST notification to the server, tailored to workflows like Deep Research, long video generation, or processing thousands of prompts with the Batch API.
Security and reliability have also been strengthened. Requests follow the Standard Webhooks specification and are signed with webhook-signature, webhook-id, and webhook-timestamp headers to ensure idempotency and prevent replay attacks. Delivery is at-least-once, and automatic retries continue for up to 24 hours.
There are two configuration methods.
- Project-wide Webhook: HMAC-based
- Per-request Webhook override: JWKS-based
This feature is currently available to all Gemini API developers, and can be integrated right away using the official Webhooks documentation and Cookbook examples.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.