> ## 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. > Get detailed information about a specific Bitcoin event log by its ID including trigger data and execution details. # Get Event Log ## OpenAPI ````yaml bitcoin/event-manager-api/openapi.json get /logs/{id} 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: /logs/{id}: get: tags: - Logs summary: Get Event Log description: |- Fetch a single event log by ID Returns the payload, status, and response of a specific event log identified by its unique `id`. operationId: EventManagerService_GetEventLog parameters: - name: id in: path required: true schema: type: string title: id responses: '200': description: Success content: application/json: schema: $ref: >- #/components/schemas/public.event_manager.v1.GetEventLogResponse default: description: Error content: application/json: schema: $ref: '#/components/schemas/connect.error' components: schemas: public.event_manager.v1.GetEventLogResponse: type: object properties: data: $ref: '#/components/schemas/public.event_manager.v1.EventLog' title: data title: GetEventLogResponse 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.EventLog: type: object properties: id: type: string title: id trigger_id: type: string title: trigger_id payload: $ref: '#/components/schemas/google.protobuf.Struct' title: payload response: type: string title: response response_status: type: integer title: response_status format: int32 status: type: string title: status title: EventLog 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. google.protobuf.Struct: type: object additionalProperties: $ref: '#/components/schemas/google.protobuf.Value' description: |- `Struct` represents a structured data value, consisting of fields which map to dynamically typed values. In some languages, `Struct` might be supported by a native representation. For example, in scripting languages like JS a struct is represented as an object. The details of that representation are described together with the proto support for the language. The JSON representation for `Struct` is JSON object. google.protobuf.Value: oneOf: - type: 'null' - type: number - type: string - type: boolean - type: array - type: object additionalProperties: true description: |- `Value` represents a dynamically typed value which can be either null, a number, a string, a boolean, a recursive struct value, or a list of values. A producer of value is expected to set one of these variants. Absence of any variant indicates an error. The JSON representation for `Value` is JSON value. securitySchemes: api-key: type: apiKey name: api-key in: header ````