Skip to content

[Bug]: Payload of push notifications is not properly encapsulated #491

@jmesnil

Description

@jmesnil

What happened?

According to § 4.3.3. Push Notification Payload, the payload of a push notification is encapsulated in the kind of payload:

POST {webhook_url}
Authorization: {authentication_scheme} {credentials}
Content-Type: application/json

{
/* StreamResponse object - one of: /
"task": { /
Task object / },
"message": { /
Message object / },
"statusUpdate": { /
TaskStatusUpdateEvent object / },
"artifactUpdate": { /
TaskArtifactUpdateEvent object */ }
}

but at the moment, the payload is directly the content of a task:

{
  "id": "task_send_with_token",
  "contextId": "ctx456",
  "status": {
    "state": "completed",
    "timestamp": "2025-11-27T11:52:51.319262Z"
  },
  "artifacts": [],
  "history": [],
  "kind": "task"
}

instead, the payload should be encapsulated with the kind of payload. In the example above, it should be:

{
  "task": {
    "id": "task_send_with_token",
    "contextId": "ctx456",
    "status": {
      "state": "completed",
      "timestamp": "2025-11-27T11:52:51.319262Z"
    },
    "artifacts": [],
    "history": [],
    "kind": "task"
  }
}

I found out this issue while working on #490 which expands the kind of payload that can be pushed by notifications.

Code of Conduct

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions