Skip to main content
POST

Overview

These endpoints allow you to configure push notifications (webhooks) for asynchronous task updates and retrieve detailed agent information for better integration planning.
Push Notifications: Webhooks enable real-time notifications about task status changes, perfect for long-running operations where polling isn’t efficient.

tasks/pushNotificationConfig/set

Configure webhook endpoints to receive push notifications about task status changes.

Request Parameters

string
required
JSON-RPC version, must be "2.0"
string
required
Unique identifier for this request
string
required
Must be "tasks/pushNotificationConfig/set"
object
required
Webhook configuration parameters

Response

string
JSON-RPC version, always "2.0"
object
Configuration result

Example


tasks/pushNotificationConfig/get

Retrieve current webhook configuration for the agent.

Request Parameters

string
required
JSON-RPC version, must be "2.0"
string
required
Unique identifier for this request
string
required
Must be "tasks/pushNotificationConfig/get"
object
Optional parameters

Response

string
JSON-RPC version, always "2.0"
object
Current webhook configuration

Example


agent/authenticatedExtendedCard

Get detailed information about the agent, including capabilities, supported features, and metadata.

Request Parameters

string
required
JSON-RPC version, must be "2.0"
string
required
Unique identifier for this request
string
required
Must be "agent/authenticatedExtendedCard"
object
Optional parameters

Response

string
JSON-RPC version, always "2.0"
object
Agent information

Example


Webhook Payload Format

When webhooks are configured, your endpoint will receive POST requests with the following payload structure:

Webhook Request Headers

Webhook Payload

Webhook Events

Sent when a task is submitted and queued for processing.Data includes: taskId, submittedAt, estimatedDuration
Sent when a task starts processing (optional, based on agent implementation).Data includes: taskId, startedAt, progress
Sent when a task completes successfully.Data includes: taskId, status.message, contextId, duration, completedAt
Sent when a task fails during processing.Data includes: taskId, status.error, duration, failedAt
Sent when a task is canceled.Data includes: taskId, reason, canceledAt

Webhook Security

Signature Verification

If you provide a secret in your webhook configuration, each webhook request will include an HMAC-SHA256 signature:

Best Practices

  • Always verify signatures when using webhook secrets
  • Use HTTPS endpoints for webhook URLs
  • Validate payload structure before processing
  • Implement idempotency using delivery IDs
  • Respond quickly (< 5 seconds) to avoid retries
  • Process asynchronously for complex operations
  • Return 2xx status codes for successful processing
  • Handle duplicate deliveries gracefully
  • Implement proper error handling for webhook processing
  • Monitor webhook delivery success rates