Skip to main content
A2A push notifications enable proactive task status updates via webhooks, while async processing with return_immediately allows non-blocking agent interactions.
A2A push notifications deliver HTTP webhooks when long-running A2A tasks change state. For real-time channel-based pub/sub between gateway and clients, see Real-Time Push Notifications.
The user submits a long-running request; the agent returns immediately and push notifications deliver status updates to the webhook.

Quick Start

1

Async Task Processing with return_immediately

Send requests that return immediately while the agent processes in the background.
2

Setting Up Push Notifications

Configure webhook notifications for automatic task status updates.

How It Works


Configuration Options

TaskPushNotificationConfig

Configure webhook delivery for task status updates.

AuthenticationInfo

Authentication details for webhook requests.

return_immediately Configuration

Blocking vs Non-blocking Requests

Default Behavior (Blocking):
Non-blocking with return_immediately:

Polling Pattern


Push Notification JSON-RPC Methods

Available Methods

Default Error Response

When push notifications are not supported:

Custom Push Notification Implementation

Complete Implementation Example

Webhook Client Configuration


Agent Card Capabilities

Push Notification Advertisement

The Agent Card declares push notification support:
When pushNotifications is false (default), all push notification methods return -32601 errors.

Common Patterns


Best Practices

Implement proper webhook handling with retries and failure logging.
Set appropriate timeouts for long-running tasks.
Always validate webhook authenticity and implement proper error handling.
Design your application to work with or without push notifications.

A2A Protocol

Core A2A server setup and configuration

A2A Tasks

Task lifecycle and state management

A2A Client

Client SDK with polling examples

Async Features

General async processing patterns