PushNotificationConfig
Defined inbindu/common/protocol/types.py:397.
Schema (exact):
authentication field is a SecurityScheme — the same discriminated union used for inbound auth on the agent. This is a deliberate choice: the agent declares how it will authenticate to your webhook using the same vocabulary you’d use to declare how callers authenticate to it.
Use Case: Webhook with bearer-token auth (SecurityScheme form)
PushNotificationAuthenticationInfo
Defined inbindu/common/protocol/types.py:417.
This type exists in the schema as an A2A-spec-compatibility shape, but
PushNotificationConfig.authentication is typed as SecurityScheme, not PushNotificationAuthenticationInfo. Use SecurityScheme when sending a config; treat this type as informational.TaskPushNotificationConfig
Defined inbindu/common/protocol/types.py:428.
Schema (exact):
longRunning: true tells the server to persist the webhook configuration across restarts so notifications still fire when the task finally completes. Wired through the JSON-RPC methods tasks/pushNotificationConfig/{set,get,list,delete} (settings.py:445-448).
How Push Notifications Work
Workflow:- Client configures push notifications when sending a message via
message/send - Server acknowledges the task and begins processing
- Server completes the task and POSTs notification to the client’s webhook URL
- Client validates the notification using the token and authentication
- Client processes the task update (e.g., updates UI, notifies user)