Configuration of a send message request.
| JSON representation |
|---|
{
"acceptedOutputModes": [
string
],
"taskPushNotificationConfig": {
object ( |
| Fields | |
|---|---|
acceptedOutputModes[] |
A list of media types the client is prepared to accept for response parts. Agents SHOULD use this to tailor their output. |
taskPushNotificationConfig |
Configuration for the agent to send push notifications for task updates. Task id should be empty when sending this configuration in a |
returnImmediately |
If |
historyLength |
The maximum number of most recent messages from the task's history to retrieve in the response. An unset value means the client does not impose any limit. A value of zero is a request to not include any messages. The server MUST NOT return more messages than the provided value, but MAY apply a lower limit. |
TaskPushNotificationConfig
A container associating a push notification configuration with a specific task.
| JSON representation |
|---|
{
"tenant": string,
"id": string,
"taskId": string,
"url": string,
"token": string,
"authentication": {
object ( |
| Fields | |
|---|---|
tenant |
Optional. Tenant ID. |
id |
The push notification configuration details. A unique identifier (e.g. UUID) for this push notification configuration. |
taskId |
The ID of the task this configuration is associated with. |
url |
Required. The URL where the notification should be sent. |
token |
A token unique for this task or session. |
authentication |
Authentication information required to send the notification. |
AuthenticationInfo
Defines authentication details, used for push notifications.
| JSON representation |
|---|
{ "scheme": string, "credentials": string } |
| Fields | |
|---|---|
scheme |
Required. HTTP Authentication Scheme from the IANA registry. Examples: |
credentials |
Push Notification credentials. Format depends on the scheme (e.g., token for Bearer). |