Maestro Official Developer Documentation

List Triggers

curl --request GET \
  --url https://xbt-mainnet.gomaestro-api.org/v0/eventmanager/triggers \
  --header 'api-key: <api-key>'

{
  "data": [
    {
      "id": "<string>",
      "name": "<string>",
      "chain": "bitcoin",
      "network": "mainnet",
      "type": "transaction",
      "webhook_url": "<string>",
      "filters": [
        {
          "key": "sender",
          "operator": "=",
          "value": "<string>"
        }
      ],
      "status": "active",
      "event_count": 123,
      "confirmations": 123
    }
  ]
}

GET

triggers

List Triggers

curl --request GET \
  --url https://xbt-mainnet.gomaestro-api.org/v0/eventmanager/triggers \
  --header 'api-key: <api-key>'

{
  "data": [
    {
      "id": "<string>",
      "name": "<string>",
      "chain": "bitcoin",
      "network": "mainnet",
      "type": "transaction",
      "webhook_url": "<string>",
      "filters": [
        {
          "key": "sender",
          "operator": "=",
          "value": "<string>"
        }
      ],
      "status": "active",
      "event_count": 123,
      "confirmations": 123
    }
  ]
}

Authorizations

api-key

string

header

required

Response

Success

data

Trigger · object[]

Show child attributes

data.id

string

data.name

string

data.chain

enum<string>

Blockchain to listen on (bitcoin)

Available options:

bitcoin

data.network

enum<string>

Network environment to listen on (mainnet)

Available options:

mainnet,

testnet

data.type

enum<string>

Trigger type, e.g., transaction

Available options:

transaction

data.webhook_url

string<uri>

Webhook URL to receive events

data.filters

Filter · object[]

Show child attributes

data.filters.key

enum<string>

Condition to match on: sender, receiver, sender_or_receiver (addresses), transaction_id, total_input_volume, fee, size, weight

Available options:

sender,

receiver,

sender_or_receiver,

transaction_id,

total_input_volume,

fee,

size,

weight

data.filters.operator

enum<string>

Condition operation: =, >, >=, <, <=. Fields like receiver and transaction_id can only be exact (=)

Available options:

=,

>,

>=,

<,

<=

data.filters.value

string

data.status

enum<string>

Status of the trigger, either active or inactive

Available options:

active,

paused

data.event_count

Number of events triggered by this trigger

data.confirmations

integer<int32>

Number of confirmations required for the transaction to be matched by this trigger

Create Trigger Get Trigger

⌘I

Blockchain Indexer API

Esplora API

Node RPC API

Mempool Monitoring API

Event Manager API

Market Price API

Wallet API

List Triggers

Authorizations

Response