Skip to content

[Feat]: Complete A2A Push Notification Protocol Support in PushNotificationSender #193

@tomboe311

Description

@tomboe311

Is your feature request related to a problem? Please describe.

The current implementation of the Push Notification Sender and the Default Push Notification Sender only supports the task payload type.
According to the A2A protocol specification, multiple additional payload types such as artifactUpdate, message, and statusUpdate are allowed. These payloads are not supported in the SDK, which leads to incomplete protocol compliance and prevents integrators from using the full set of push notification features defined by the A2A standard.

Describe the solution you'd like

I would like the SDK to fully implement the A2A Push Notification Protocol by supporting all payload types defined in the specification. This includes:

  • Extending the payload type definitions beyond task
  • Implementing support for artifactUpdate, message, statusUpdate, and any other protocol-defined payloads
  • Ensuring proper validation of payload structure and required fields
  • Updating PushNotificationSender and DefaultPushNotificationSender to handle these payload types consistently

This will ensure full protocol compliance and enable developers to use the complete notification feature set.

Describe alternatives you've considered

Implementing only the payload types needed for specific use cases, but this would again result in partial protocol support and lead to inconsistencies in the future.
Creating custom sender implementations outside the SDK, but this fragments the ecosystem and duplicates effort.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions