Webhooks

Overview

Aegis receives webhook notifications from Circle whenever a transaction state changes onchain. These webhooks update the internal audit log and transaction records automatically.

Webhooks in Aegis are an internal system mechanism. Your agent does not need to set up webhook endpoints. Aegis handles incoming Circle notifications automatically and updates your agent’s transaction status and balance accordingly.

How It Works

When your agent initiates a transfer, bridge, or payment, Aegis creates the transaction via Circle DCW

Circle processes the transaction onchain

When the transaction is confirmed (or fails), Circle sends a webhook notification to the Aegis server

Aegis updates the transaction status in the audit log

Your agent can query the updated status via the relevant API endpoint

Event	Description
Transaction confirmed	A transfer or contract call has been confirmed onchain
Transaction failed	A transaction failed during onchain execution
Bridge completed	A CCTP bridge transfer has been finalized on the destination chain

Event

Description

Transaction confirmed

A transfer or contract call has been confirmed onchain

Transaction failed

A transaction failed during onchain execution

Bridge completed

A CCTP bridge transfer has been finalized on the destination chain

Polling for Updates

Since webhooks are handled internally, your agent should poll for status updates when waiting for transaction confirmation:

# Check transfer status via the audit ledger
curl -X GET https://api.aegisintent.xyz/v1/actions/audit/ledger \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "X-Aegis-Email: agent@example.com"

# Check bridge status specifically
curl -X POST https://api.aegisintent.xyz/v1/actions/bridge/status \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "X-Aegis-Email: agent@example.com" \
  -H "Content-Type: application/json" \
  -d '{"txHash": "0x892a01f80e0cdbb..."}'

For transfers on Arc Testnet, confirmation typically takes a few seconds. For crosschain bridges via CCTP, allow up to 15 minutes for finality on the destination chain.

Start Here

How Aegis Works

Agent Actions

Operations

Overview

How It Works

Supported Events

Polling for Updates

​Overview

​How It Works

​Supported Events

​Polling for Updates

Overview

How It Works

Supported Events

Polling for Updates