> ## Documentation Index > Fetch the complete documentation index at: https://docs.gomaestro.org/llms.txt > Use this file to discover all available pages before exploring further. > List all active event triggers configured for your account, with details about filters, webhooks, and trigger status. # List Triggers ## OpenAPI ````yaml bitcoin/event-manager-api/openapi.json get /triggers openapi: 3.1.0 info: title: Bitcoin - Event Manager API description: >- Maestro's Bitcoin Event Manager API provides a programmable webhook infrastructure for tracking Bitcoin events like transactions, address activity, and related on-chain changes. It allows developers to configure event managers and attach triggers that define what blockchain events to listen for, delivering relevant data to a specified webhook in real time. This API is ideal for alerting systems, real-time monitoring dashboards, and backend processes that need to react to blockchain state changes. ### Key Features: - **Granular Triggers:** Set up address-based triggers for sender, receiver, or transaction events with optional filters for additional precision. - **Real-Time Webhook Delivery:** Events are pushed to your provided webhook URL the moment matching transactions are detected. - **Structured Logging:** Access detailed logs for each event fired, including payload, status, and webhook response. - **Flexible Lifecycle Control:** Fully manage, update, or delete event managers and their triggers via API endpoints. ### Key Benefits for Developers: Developers can automate transaction monitoring and event handling without running full nodes or maintaining custom indexers. The Event Manager API streamlines webhook setup for Bitcoin applications, enabling responsive, event-driven architectures. It’s especially valuable for wallet notifications, transaction confirmations, backend synchronization, and building reactive user experiences without polling the chain. license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html version: 0.5.1 servers: - url: https://xbt-mainnet.gomaestro-api.org/v0/eventmanager description: Bitcoin Mainnet API - url: https://xbt-testnet.gomaestro-api.org/v0/eventmanager description: Bitcoin Testnet API security: - api-key: [] tags: - name: EventManagerService paths: /triggers: get: tags: - Triggers summary: List Triggers description: |- List all triggers Returns all individual triggers associated with your event managers. operationId: EventManagerService_ListTriggers responses: '200': description: Success content: application/json: schema: $ref: >- #/components/schemas/public.event_manager.v1.ListTriggersResponse default: description: Error content: application/json: schema: $ref: '#/components/schemas/connect.error' components: schemas: public.event_manager.v1.ListTriggersResponse: type: object properties: data: type: array items: $ref: '#/components/schemas/public.event_manager.v1.Trigger' title: data title: ListTriggersResponse additionalProperties: false connect.error: type: object properties: code: type: string examples: - not_found enum: - canceled - unknown - invalid_argument - deadline_exceeded - not_found - already_exists - permission_denied - resource_exhausted - failed_precondition - aborted - out_of_range - unimplemented - internal - unavailable - data_loss - unauthenticated description: >- The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code]. message: type: string description: >- A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client. detail: $ref: '#/components/schemas/google.protobuf.Any' title: Connect Error additionalProperties: true description: >- Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation public.event_manager.v1.Trigger: type: object properties: id: type: string title: id name: type: string title: name chain: type: string examples: - bitcoin title: chain enum: - bitcoin description: Blockchain to listen on (bitcoin) network: type: string examples: - mainnet title: network enum: - mainnet - testnet description: Network environment to listen on (mainnet) type: type: string examples: - transaction title: type enum: - transaction description: Trigger type, e.g., transaction webhook_url: type: string examples: - https://webhook.site/your-endpoint title: webhook_url format: uri description: Webhook URL to receive events filters: type: array items: $ref: '#/components/schemas/public.event_manager.v1.Filter' title: filters status: type: string examples: - active title: status enum: - active - paused description: Status of the trigger, either active or inactive event_count: type: - integer - string examples: - '40' title: event_count format: int64 description: Number of events triggered by this trigger confirmations: type: integer examples: - '5' title: confirmations format: int32 description: >- Number of confirmations required for the transaction to be matched by this trigger title: Trigger additionalProperties: false google.protobuf.Any: type: object properties: type: type: string value: type: string format: binary debug: type: object additionalProperties: true additionalProperties: true description: >- Contains an arbitrary serialized message along with a @type that describes the type of the serialized message. public.event_manager.v1.Filter: type: object properties: key: type: string examples: - sender title: key enum: - sender - receiver - sender_or_receiver - transaction_id - total_input_volume - fee - size - weight description: >- Condition to match on: sender, receiver, sender_or_receiver (addresses), transaction_id, total_input_volume, fee, size, weight operator: type: string examples: - '=' title: operator enum: - '=' - '>' - '>=' - < - <= description: >- Condition operation: =, >, >=, <, <=. Fields like receiver and transaction_id can only be exact (=) value: type: string title: value title: Filter additionalProperties: false description: >+ For key in [sender, receiver, sender_or_receiver, transaction_id], operator must be '=': ``` !(this.key in ['sender', 'receiver', 'sender_or_receiver', 'transaction_id']) || this.operator == '=' ``` securitySchemes: api-key: type: apiKey name: api-key in: header ````