> ## Documentation Index > Fetch the complete documentation index at: https://developers.stellar.org/llms.txt > Use this file to discover all available pages before exploring further. # Retrieve Related Transactions > This endpoint represents successful transactions referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time. > [!TIP] > > **Supports Streaming** > > This endpoint supports streaming. To read more about this, visit the [streaming section](https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/streaming.md). ## OpenAPI ````yaml openapi/horizon/bundled.yml GET /liquidity_pools/{liquidity_pool_id}/transactions openapi: 3.1.0 info: title: Horizon version: 0.0.1 summary: >- Horizon provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by Stellar Core. This API serves the bridge between apps and Stellar Core. Projects like wallets, decentralized exchanges, and asset issuers use Horizon to submit transactions, query an account balance, or stream events like transactions to an account. description: > Horizon provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by [Stellar Core](https://developers.stellar.org/network/core-node). This API serves the bridge between apps and Stellar Core. Projects like wallets, decentralized exchanges, and asset issuers use Horizon to submit transactions, query an account balance, or stream events like transactions to an account. Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](https://developers.stellar.org/docs/tools/sdks). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls. This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](https://developers.stellar.org/network/core-node) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). termsOfService: https://stellar.org/terms-of-service contact: name: Stellar Development Foundation url: https://stellar.org email: hello@stellar.org license: name: Apache 2.0 identifier: Apache-2.0 servers: - url: https://horizon-testnet.stellar.org description: The Testnet Network - url: https://horizon-futurenet.stellar.org description: The Futurenet network security: [] tags: - name: Accounts description: >- Users interact with the Stellar network through accounts. Everything else in the ledger—assets, offers, trustlines, etc. are owned by accounts, and accounts must authorize all changes to the ledger through signed transactions. - name: Assets description: >- Assets are representations of value issued on the Stellar network. An asset consists of a type, code, and issuer. - name: Claimable Balances description: >- A Claimable Balance represents the transfer of ownership of some amount of an asset. Claimable balances provide a mechanism for setting up a payment which can be claimed in the future. This allows you to make payments to accounts which are currently not able to accept them. - name: Effects description: >- Effects represent specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are. - name: Fee Stats description: >- Fee stats are used to predict what fee to set for a transaction before submitting it to the network. - name: Liquidity Pools description: >- Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading. - name: Ledgers description: >- Each ledger stores the state of the network at a point in time and contains all the changes - transactions, operations, effects, etc. - to that state. - name: Offers description: >- Offers are statements about how much of an asset an account wants to buy or sell. - name: Operations description: >- Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction. - name: Order Books description: An order book is a collections of offers for a specific pair of assets. - name: Paths description: >- Paths provide information about potential path payments. A path can be used to populate the necessary fields for a path payment operation. - name: Payments description: >- Payments are objects that represent balance transfer from one address to another. Payments are submitted to the Stellar network grouped in a Transaction. - name: Trade Aggregations description: >- A trade aggregation represents aggregated statistics on an asset pair (base and counter) for a specific time period. Trade aggregations are useful to developers of trading clients and provide historical trade data. - name: Trades description: >- When an offer is fully or partially fulfilled, a trade happens. Trades can also be caused by successful path payments, because path payments involve fulfilling offers. A trade occurs between two parties—base and counter. Which is which is either arbitrary or determined by the calling query. - name: Transactions description: >- Transactions are commands that modify the ledger state and consist of one or more operations. paths: /liquidity_pools/{liquidity_pool_id}/transactions: get: tags: - Liquidity Pools summary: Retrieve Related Transactions description: >- This endpoint represents successful transactions referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time. operationId: LPRetrieveRelatedTransactions parameters: - $ref: '#/components/parameters/LiquidityPoolParamId' - $ref: '#/components/parameters/CursorParam' - $ref: '#/components/parameters/OrderParam' - $ref: '#/components/parameters/LimitParam' - $ref: '#/components/parameters/IncludeFailedParam' responses: '200': description: Success content: application/json: schema: allOf: - $ref: '#/components/schemas/Links' - $ref: '#/components/schemas/Transaction' examples: LPRetrieveRelatedTransactions: $ref: '#/components/examples/LPRetrieveRelatedTransactions' components: parameters: LiquidityPoolParamId: name: liquidity_pool_id in: path required: true description: A unique identifier for this liquidity pool. schema: type: string example: 33f3c53f53e6d1f1f13d7f9d9b58c2cb5c7e0b0a4d1d3c5b2a6f7e8d9c0b1a2f CursorParam: name: cursor in: query required: false description: >- A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record. schema: type: integer example: 6606617478959105 OrderParam: name: order in: query required: false description: >- A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`. schema: type: string enum: - asc - desc LimitParam: name: limit in: query required: false description: >- The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10. schema: type: integer example: 10 IncludeFailedParam: name: include_failed in: query required: false description: >- Set to true to include failed operations in results. Options include true and false. schema: type: boolean enum: - true - false schemas: Links: type: object properties: _links: type: object properties: self: $ref: '#/components/schemas/link' next: $ref: '#/components/schemas/link' prev: $ref: '#/components/schemas/link' Transaction: type: object properties: _embedded: type: object properties: records: type: array items: type: object properties: memo: type: string _links: type: object properties: self: $ref: '#/components/schemas/link' account: $ref: '#/components/schemas/link' ledger: $ref: '#/components/schemas/link' operations: $ref: '#/components/schemas/link' effects: $ref: '#/components/schemas/link' precedes: $ref: '#/components/schemas/link' succeeds: $ref: '#/components/schemas/link' transaction: $ref: '#/components/schemas/link' required: - self - account - ledger - operations - effects - precedes - succeeds - transaction id: $ref: '#/components/schemas/id' paging_token: type: string successful: type: boolean hash: type: string ledger: type: integer format: int32 created_at: type: string source_account: $ref: '#/components/schemas/address' account_muxed: type: string account_muxed_id: type: string source_account_sequence: type: string fee_account: $ref: '#/components/schemas/address' fee_account_muxed: $ref: '#/components/schemas/address' fee_account_muxed_id: type: string fee_charged: type: string max_fee: type: string operation_count: type: integer format: int32 envelope_xdr: type: string result_xdr: type: string result_meta_xdr: type: string fee_meta_xdr: type: string memo_type: type: string signatures: $ref: '#/components/schemas/signatures' preconditions: $ref: '#/components/schemas/TransactionPreconditions' fee_bump_transaction: $ref: '#/components/schemas/FeeBumpTransaction' inner_transaction: $ref: '#/components/schemas/InnerTransaction' required: - id - paging_token - successful - hash - ledger - created_at - source_account - source_account_sequence - fee_account - fee_charged - max_fee - operation_count - envelope_xdr - result_xdr - result_meta_xdr - memo_type - signatures link: type: object properties: href: type: string format: link templated: type: boolean required: - href id: type: string address: type: string pattern: G[A-Z0-9]{55} signatures: type: array items: type: string pattern: G[A-Z0-9]{55} TransactionPreconditions: type: object properties: timebounds: $ref: '#/components/schemas/TransactionPreconditionsTimebounds' ledgerbounds: $ref: '#/components/schemas/TransactionPreconditionsLedgerbounds' min_account_sequence: type: string min_account_sequence_age: type: string min_account_sequence_ledger_gap: type: integer format: uint32 extra_signers: type: array items: type: string FeeBumpTransaction: type: object properties: hash: $ref: '#/components/schemas/hash' signatures: $ref: '#/components/schemas/signatures' InnerTransaction: type: object properties: hash: $ref: '#/components/schemas/hash' signatures: $ref: '#/components/schemas/signatures' max_fee: type: string TransactionPreconditionsTimebounds: type: object properties: min_time: type: string max_time: type: string TransactionPreconditionsLedgerbounds: type: object properties: min_ledger: type: string max_ledger: type: string hash: type: string examples: LPRetrieveRelatedTransactions: value: _links: self: href: >- https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=&limit=2&order=asc next: href: >- https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=120192370561220608&limit=2&order=asc prev: href: >- https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=120192344791343104&limit=2&order=desc _embedded: records: - _links: self: href: >- https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908 account: href: >- https://horizon-testnet.stellar.org/accounts/GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7 ledger: href: https://horizon-testnet.stellar.org/ledgers/895788 operations: href: >- https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908/operations templated: true effects: href: >- https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908/effects templated: true precedes: href: >- https://horizon-testnet.stellar.org/transactions?order=asc&cursor=3847380164161536 succeeds: href: >- https://horizon-testnet.stellar.org/transactions?order=desc&cursor=3847380164161536 transaction: href: >- https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908 id: 2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908 paging_token: '3847380164161536' successful: true hash: 2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908 ledger: 895788 created_at: '2021-08-09T20:53:11Z' source_account: GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7 source_account_sequence: '3847371574214658' fee_account: GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7 fee_charged: '10000' max_fee: '10001' operation_count: 1 envelope_xdr: >- AAAAAgAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAJxEADasqAAAAAgAAAAAAAAAAAAAAAQAAAAEAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAGAAAAAVNFQwAAAAAAm6XFaVsf8OSuS9C9gMplyTjagE9jAnnqwxSDJ6fin6IAsaK8LsUAAAAAAAAAAAAB9uVOlAAAAECXmRsoXmRiJjUrtbkDZYRnzac5s1CVV4g2RlIgBIuQty21npz3A1VhUcSmAx+GmsyGxVFvIrcdstTawJlmy9kF result_xdr: AAAAAAAAJxAAAAAAAAAAAQAAAAAAAAAGAAAAAAAAAAA= result_meta_xdr: >- AAAAAgAAAAIAAAADAA2rLAAAAAAAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAAGtJNDAANqyoAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAA2rLAAAAAAAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAAGtJNDAANqyoAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAIAAAABAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAADassAAAAAQAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAFTRUMAAAAAAJulxWlbH/DkrkvQvYDKZck42oBPYwJ56sMUgyen4p+iAAAAAAAAAAAAsaK8LsUAAAAAAAEAAAAAAAAAAAAAAAA= fee_meta_xdr: >- AAAAAgAAAAMADasrAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0nQcAA2rKgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA== memo_type: none signatures: - >- l5kbKF5kYiY1K7W5A2WEZ82nObNQlVeINkZSIASLkLcttZ6c9wNVYVHEpgMfhprMhsVRbyK3HbLU2sCZZsvZBQ== ````