On May 4, 2026, Google announces that the Gemini API now supports event — driven webhooks that send real-time HTTP POST

Event — driven webhooks push HTTP POST notifications when tasks finish, removing inefficient polling and reducing latency for long-running Gemini API jobs.

On May 4, 2026, Google announced that the Gemini API now supports event — driven webhooks that send real-time HTTP POST payloads to developer endpoints when tasks complete. The launch was described in a post by Lucia Loher (Product Manager, Gemini API) and Hussein Hassan Harrirou (Engineering, Gemini API) and is aimed at workflows that outlive a single synchronous request.

The new webhooks follow the Standard Webhooks specification and include the delivery controls expected for production use. Each webhook request is signed and carries webhook — signature, webhook — id, and webhook — timestamp headers intended to support idempotency and guard against replay attacks. Google states it will make at-least-once delivery and will automatically retry failed deliveries for up to 24 hours.

Configuration can be set globally at the project level using HMAC, or overridden per request with JWKS to allow dynamic routing and per-job destinations. The company also published a Webhooks guide listing the full event catalog and endpoint security recommendations, plus a Cookbook with hands — on examples and a Python SDK snippet showing dynamic webhook configuration for batch tasks.

The feature targets a shift in Gemini usage toward agentic, high-volume processing: Google cited Deep Research tasks, long video generation, and Batch API jobs that may process thousands of prompts and run for minutes or hours. Those workloads once required continuous polling to detect completion, which adds latency and compute overhead on client servers; the push model reduces wasted API calls and shortens end-to-end notification time for dependent workflows.

Implementers should still design for duplicate deliveries and replay protection because of the at-least-once guarantee and retry window. The 24 — hour retry semantics also affect how servers track job state and backfill missed events if an endpoint is temporarily unreachable. The webhooks capability is available now to all developers using the Gemini API.