What changed
Google introduced Webhooks in the Gemini API on May 4. Instead of repeatedly polling operation endpoints, developers can now receive an HTTP POST as soon as an async job finishes.
According to the official webhooks documentation, the new callbacks work for Batch jobs, Interactions, and video generation. Google also supports both project-level static webhooks and per-request dynamic webhooks, so teams can route background jobs through shared infrastructure or job-specific endpoints.
Why it matters
This is a meaningful product update for builders, not just a transport tweak. Gemini's async surfaces are aimed at work that can run for minutes or hours. Google's Batch API docs describe Batch as asynchronous, priced at 50% of the standard cost, and designed for large-scale, non-urgent workloads with a target turnaround time of 24 hours.
That made polling a real operational tax:
- extra requests and monitoring noise
- slower handoffs into downstream steps
- more queue and retry plumbing in your own app
- harder-to-manage long-running agent workflows
Webhooks turn those jobs into cleaner event-driven flows. A batch report, research run, long interaction, or video generation task can now trigger the next step immediately instead of waiting for your scheduler to notice that the operation finished.
The implementation details worth noticing
Two parts of the rollout stand out.
First, Google says the feature follows the Standard Webhooks specification, which should reduce custom verification work for teams that already use the same pattern elsewhere. Second, delivery is at-least-once with automatic retries for up to 24 hours, which is the right default for long-running jobs but still means consumers need idempotent handlers.
The docs also split the feature into two useful modes:
- static webhooks for project-level integrations secured with a signing secret
- dynamic webhooks for request-level routing, which fits agent orchestration and multitenant queues better
Practical take for builders
If you are building with Gemini, this is a good moment to move background workflows away from status polling:
- Keep request creation synchronous.
- Hand long jobs to Batch, Interactions, or video generation.
- Verify webhook signatures at the edge.
- Make your callback handler idempotent.
- Trigger the next job, notification, or database update from the callback.
The headline is simple: Google is making Gemini feel more like production infrastructure for agents, not just a model endpoint.