Skip to main content
PUT
/
v1
/
w3s
/
contracts
/
monitors
/
{id}
Update an Event Monitor
curl --request PUT \
  --url https://api.circle.com/v1/w3s/contracts/monitors/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "isEnabled": false
}
'
{
  "data": {
    "eventMonitor": {
      "id": "e3c998a5-bdf1-4f3e-812f-24da238c0fff",
      "blockchain": "MATIC-AMOY",
      "contractAddress": "0x1e124d7384cd34448ea5907bd0052a79355ab5eb",
      "eventSignature": "Transfer(address indexed from, address indexed to, uint256 value)",
      "eventSignatureHash": "0xd3d3dd4b1fd3e53f94deb24e763485b4c925345c5abfa9ad529c67aa55a3b784",
      "isEnabled": true
    }
  }
}

Authorizations

​
Authorization
string
header
required

Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are required to make a successful request.

Headers

​
X-Request-Id
string<uuid>

Developer-provided identifier for this request, used for tracing requests in Wallets API logs and the Developer Console, and when communicating with Circle Support. Must be a UUID to appear in logs. Non-UUID values are accepted by the API but are ignored by logging and tracing systems.

A unique identifier, which can be helpful for identifying a request when communicating with Circle support.

Example:

"2adba88e-9d63-44bc-b975-9b6ae3440dde"

Path Parameters

​
id
string
required

Event Monitor ID.

Body

application/json

Update Event Monitor Request

​
isEnabled
boolean
required

Indicates whether the event monitor should be active (true) or inactive (false).

Response

Event monitor updated successfully.

​
data
object
required