Skip to main content
POST
/
api
/
intents
/
{intentId}
/
events
Post transaction hash after broadcast
curl --request POST \
  --url https://app.mandate.md/api/intents/{intentId}/events \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "txHash": "0x9f2e4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f"
}
'
{
  "intentId": "9e5f1a2b-3c4d-5e6f-7a8b-9c0d1e2f3a4b",
  "status": "broadcasted",
  "txHash": "0x9f2e4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f"
}

Documentation Index

Fetch the complete documentation index at: https://docs.mandate.md/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Runtime key issued at agent registration. Prefixed with mndt_live_ (mainnet) or mndt_test_ (testnet). Pass as Authorization: Bearer mndt_test_....

Path Parameters

​
intentId
string<uuid>
required

The intent ID returned from validation.

Body

application/json
​
txHash
string
required

The on-chain transaction hash.

Pattern: ^0x[a-fA-F0-9]{64}$

Response

Event recorded, intent transitioned to broadcasted.

​
intentId
string<uuid>
required
​
status
enum<string>
required
Available options:
broadcasted
​
txHash
string
required