> ## 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.

# Migrate from Horizon to RPC

> Applications using [Horizon's REST-like API] will need to be updated to use the [RPC JSON-RPC API] when migrating from [Horizon] to [RPC].

Applications using [Horizon's REST-like API] will need to be updated to use the [RPC JSON-RPC API] when migrating from [Horizon] to [RPC]. This guide provides an overview of the key differences between the two APIs and how to migrate your application.

## Request / Response Format

Horizon's REST-like API uses HTTP methods and status codes to communicate with clients. Responses are JSON in the HAL format. See [Horizon's Response Format].

RPC's JSON-RPC API uses JSON-RPC 2.0 to communicate with clients. Requests to the API are JSON objects that contain one or more method invocations. Responses are also JSON objects that contain a result for each invocation in the request. See [JSON-RPC].

Both formats utilise JSON for the overall structure which are relatively simple and do not require any special client code, although there are client [SDKs] available. Some values contained within are XDR encoded and can be decoded using Stellar [SDKs].

The two APIs also return different response shapes. See [Response Differences](#response-differences) after the endpoint mapping.

## Endpoint Mapping

Applications that use the following Horizon endpoints can typically migrate directly to the RPC using the referenced methods.

Endpoints without mappings do not have a direct replacement in the RPC API. To build similar functionality in an application, please consider partnering with an indexer or using the information listed below to build your own indexed representation of horizon endpoints. Consider using other [Data] products for analytics use cases.

| Horizon Endpoint | Corresponding RPC Method(s) | Indexer Equivalent | Analytics Resources |
| - | - | - | - |
| [`GET /`] | [`getLatestLedger`] [`getVersionInfo`] [`getHealth`] [`getNetwork`] | Not applicable | [Analyst Guide](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide) |
| [`GET /ledgers`] | [`getLedgers`] | Create a [`getLedgers`] with full history, using [Galexie](https://developers.stellar.org/docs/data/indexers/build-your-own/galexie), to build a historical ledger view. | [Ledgers](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#ledgers) |
| [`GET /ledgers/{seq}`] | [`getLedgers`] (with filter for sequence) | Use a [`getLedgers`] view with full history, filtered by ledger sequence | [Ledgers](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#ledgers) |
| [`GET /ledgers/{seq}/transactions`] | [`getTransactions`] (with filter for ledger sequence) | Use [`getTransactions`] with ledger sequence filtering to retrieve transactions for a specific ledger | [Transactions](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#transactions) |
| [`GET /ledgers/{seq}/operations`] | [`getTransactions`] | Use [`getTransactions`] for the given ledger, then parse the transaction's XDR for individual operations. | [Operations](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#operations) |
| [`GET /ledgers/{seq}/payments`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] (CAP-67 asset events, available since Protocol 23 on nodes that emit classic events) and parse [`getTransactions`] meta XDR to tie those events back to individual operations. | [Payments](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#payments) |
| [`GET /ledgers/{seq}/effects`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] for the effects CAP-67 models (asset movement and trustline authorization), and parse [`getTransactions`] meta XDR for every other effect type. | [Effects](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#effects) |
| [`POST /transactions`] | [`sendTransaction`] | Not applicable | Not applicable |
| [`POST /transactions_async`] | [`sendTransaction`] | Not applicable | Not applicable |
| [`GET /transactions`] | [`getTransactions`] | Use [`getTransactions`] to build a historical transaction list | [Transactions](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#transactions) |
| [`GET /transactions/{hash}`] | [`getTransaction`] | Use getTransaction to retrieve a specific transaction by its hash | [Transactions](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#transactions) |
| [`GET /transactions/{hash}/operations`] | [`getTransaction`] | Filter [`getTransaction`] by hash and then parse its XDR for operations | [Operations](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#operations) |
| [`GET /transactions/{hash}/payments`] | No direct RPC equivalent; use [`getEvents`] or parse [`getTransactions`] | Filter [`getTransaction`] by hash and analyze its events and operation types to identify payments. | [Payments](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#payments) |
| [`GET /transactions/{hash}/effects`] | No direct RPC equivalent; use [`getEvents`] or parse [`getTransactions`] | Filter [`getTransaction`] by hash and analyze its events and metadata for relevant data. | [Effects](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#effects) |
| [`GET /operations`] | [`getTransactions`] | Ingest all historical ledgers/transactions and build and build a view of operations for filtering. | [Operations](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#operations) |
| [`GET /operations/{id}`] | No direct RPC equivalent | Store Horizon's operation ID and map it back to the ledger sequence and transaction index to retrieve the relevant transaction via [`getTransactions`]. | [Operations](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#operations) |
| [`GET /operations/{id}/effects`] | No direct RPC equivalent | Retrieve the operation by ID (as above) and then parse its associated transaction and events for effects. | [Effects](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#effects) |
| [`GET /fee_stats`] | [`getFeeStats`] [`simulateTransaction`] | Indexed data not recommended. | [Fee Stats](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#fee-stats) |
| [`GET /accounts`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of accounts. | [Accounts](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#accounts) |
| [`GET /accounts/{address}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] for a specific account address. Note: RPC will not provide trustline information associated with the account directly, as Horizon does. You will need to derive this from ledger entries. See [Example: Account Balances](#example-account-balances). | [Accounts](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#accounts) |
| [`GET /claimable_balances`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of claimable balances. | [Claimable Balances](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#claimable-balances) |
| [`GET /claimable_balances/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific claimable balance by ID. | [Claimable Balances](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#claimable-balances) |
| [`GET /claimable_balances/{id}/transactions`] | No direct RPC equivalent | Trace transactions that interact with the specific claimable balance ID from their historical ledger data. | [Claimable Balances](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#claimable-balances) |
| [`GET /claimable_balances/{id}/operations`] | No direct RPC equivalent | trace operations related to the specific claimable balance ID from your historical ledger data. | [Claimable Balances](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#claimable-balances) |
| [`GET /liquidity_pools`] | No direct RPC equivalent | ingest all ledger history via [`getLedgers`] to build and maintain a complete list of liquidity pools. | [Liquiditity Pools](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#liquidity-pools) |
| [`GET /liquidity_pools/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific liquidity pool by ID. | [Liquiditity Pools](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#liquidity-pools) |
| [`GET /liquidity_pools/{id}/transactions`] | No direct RPC equivalent | Trace transactions that interact with the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#liquidity-pools) |
| [`GET /liquidity_pools/{id}/operations`] | No direct RPC equivalent | Trace operations related to the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#liquidity-pools) |
| [`GET /liquidity_pools/{id}/effects`] | No direct RPC equivalent | Trace effects related to the specific liquidity pool ID from their historical ledger data. | [Liquiditity Pools](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#liquidity-pools) |
| [`GET /liquidity_pools/{id}/trades`] | No direct RPC equivalent | Infer trades related to the specific liquidity pool ID from historical ledger data (e.g., from [`getEvents`] and [`getTransactions`] metadata). | [Liquiditity Pools](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#liquidity-pools) |
| [`GET /offers`] | No direct RPC equivalent | Ingest all ledger history via [`getLedgers`] to build and maintain a complete list of offers. | [Offers](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#offers) |
| [`GET /offers/{id}`] | [`getLedgerEntries`] | Use [`getLedgerEntries`] to retrieve a specific offer by ID. | [Offers](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#offers) |
| [`GET /offers/{id}/trades`] | No direct RPC equivalent | Infer trades related to the specific offer ID from historical ledger data (e.g., from [`getEvents`] and [`getTransactions`] metadata). | [Offers](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#offers) |
| [`GET /payments`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] (CAP-67 asset events) and process [`getTransactions`] metadata for payment-like operations across all history. | [Payments](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#payments) |
| [`GET /effects`] | [`getEvents`] [`getTransactions`] ⚠️ | Use [`getEvents`] for the effects CAP-67 models, and process [`getTransactions`] metadata to derive the remaining effect types across all history. | [Effects](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#effects) |
| [`GET /trades`] | [`getEvents`] [`getTransactions`] ⚠️ | Infer trades from [`getEvents`] and [`getTransactions`] metadata across all history, as there is no direct "trade event" in RPC. | [Trades](https://developers.stellar.org/docs/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.md#trades) |

> [!TIP]
>
> The \[`getTransactions`] method can be used to retrieve events batched by transaction. The events are contained in the meta XDR of the transaction (field `resultMetaXdr`).

> [!WARNING]
>
> The \[`getEvents`] method is not a direct replacement for Horizon's endpoints.
>
> Since \[CAP-67] shipped in Protocol 23, the method can return events from classic operations as well as from contracts. Those unified asset events are emitted as `transfer`, `mint`, `burn`, `clawback`, `fee`, and `set_authorized`, so a single stream can cover the movement of assets and changes to trustline authorization.
>
> Classic events are not on by default. They are only present if the Stellar Core instance backing the RPC runs with `EMIT_CLASSIC_EVENTS=true`. If you also need to cover ledgers from Protocol 22 and earlier, that additionally requires `BACKFILL_STELLAR_ASSET_EVENTS=true`. If you run your own RPC, set what your history range needs before relying on this mapping. If you use a provider, confirm with them. See [Events](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures/events.md) for more detail.
>
> That is still narrower than Horizon's effects. Anything CAP-67 does not model, such as signer updates, data entry changes, sequence number bumps, and offer management, has to come from the meta XDR of the transaction. The \[`getTransactions`] method returns that meta XDR (field `resultMetaXdr`), which also contains events from contracts.

## Response Differences

The [endpoint mapping](#endpoint-mapping) above pairs each Horizon endpoint with an RPC method, but the two responses do not have the same shape. Horizon curates the ledger for you. RPC hands you the ledger entry as the protocol stores it. This section compares one pair, [`GET /accounts/{address}`] and [`getLedgerEntries`], because most migrations hit it first. The rows about missing keys, the 200-key limit, and paging describe `getLedgerEntries` only. [`getTransactions`], [`getLedgers`], and [`getEvents`] page with a cursor and a limit. Plan for these differences before you swap one call for the other.

| Concern | Horizon `GET /accounts/{address}` | RPC `getLedgerEntries` |
| - | - | - |
| Shape | One aggregated resource per endpoint | One ledger entry for each requested key that exists |
| Amounts | Decimal string with seven places, such as `"1252.7872975"` | Signed 64-bit integer of stroops, sent as a string, such as `"12527872975"` |
| Encoding | Parsed JSON fields | Base64 XDR, or JSON when you pass `xdrFormat` |
| Flags and thresholds | Named booleans and named thresholds | A raw `uint32` bitmask and a four-byte hex string |
| Entry not found | HTTP `404` | HTTP `200`, and the key is absent from `entries`, which is empty when no key exists |
| Batching | One account per request, with no paging. The HAL `_links` lead to separate collections such as transactions | Up to 200 keys per call, with no paging. Split larger sets into several calls |

The RPC column describes the decoded ledger entry. A default response holds those fields inside the base64 XDR, so you see them only after you decode it, or after you ask for the JSON view with `xdrFormat`.

### Example: Account Balances

Horizon's [`GET /accounts/{address}`] response is an aggregation. It joins the account entry with the account's trustline entries. The [`AccountEntry`] structure holds no trustlines of its own. It holds only a count of the account's sub-entries. So, for balances, one Horizon call becomes a [`getLedgerEntries`] call with an account key plus one trustline key per non-native balance, including liquidity pool shares, and you must already know each asset. The XLM balance is in the account entry itself, so it needs no trustline key. Horizon's `data` map comes from separate data entries, so each account data key you need is one more key in the request. A call takes at most 200 keys, so an account with many trustlines or data entries needs more than one call.

The example below uses a Testnet account. A [Testnet data reset](https://developers.stellar.org/docs/networks.md#testnet-and-futurenet-data-reset) clears it, so use your own account and asset to follow along. This Horizon request returns both balances at once:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl "https://horizon-testnet.stellar.org/accounts/GA2242THTLFWPCW2SF3TTLDWJ3C543UUNFTFIMDJUZYXNW2EMEAXZBRH"
```

Horizon answers with one resource. The response below is trimmed to the fields this comparison uses:

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "subentry_count": 1,
  "thresholds": {
    "low_threshold": 0,
    "med_threshold": 0,
    "high_threshold": 0
  },
  "flags": {
    "auth_required": false,
    "auth_revocable": false,
    "auth_immutable": false,
    "auth_clawback_enabled": false
  },
  "balances": [
    {
      "balance": "1252.7872975",
      "limit": "922337203685.4775807",
      "is_authorized": true,
      "asset_type": "credit_alphanum4",
      "asset_code": "USDC",
      "asset_issuer": "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
    },
    {
      "balance": "9009.2998203",
      "asset_type": "native"
    }
  ],
  "signers": [
    {
      "weight": 1,
      "key": "GA2242THTLFWPCW2SF3TTLDWJ3C543UUNFTFIMDJUZYXNW2EMEAXZBRH",
      "type": "ed25519_public_key"
    }
  ]
}
```

The same data over RPC takes two keys. The first key is the account, the second is the USDC trustline. See [Building ledger keys](https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries.md#types-of-ledgerkeys) for how to build each one.

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "getLedgerEntries",
  "params": {
    "keys": [
      "AAAAAAAAAAA1rmpnmstnitqRdzmsdk7F3m6UaWZUMGmmcXbbRGEBfA==",
      "AAAAAQAAAAA1rmpnmstnitqRdzmsdk7F3m6UaWZUMGmmcXbbRGEBfAAAAAFVU0RDAAAAAEI+fQXy7K+/7BkrIVo/G+lq7bjY5wJUq+NBPgIH3lay"
    ],
    "xdrFormat": "json"
  }
}
```

RPC answers with one entry for each key it finds. Each entry repeats the key it answers, in the `keyJson` field. This is the `result` object of that response, trimmed the same way:

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "entries": [
    {
      "keyJson": {
        "account": {
          "account_id": "GA2242THTLFWPCW2SF3TTLDWJ3C543UUNFTFIMDJUZYXNW2EMEAXZBRH"
        }
      },
      "dataJson": {
        "account": {
          "balance": "90092998203",
          "num_sub_entries": 1,
          "flags": 0,
          "thresholds": "01000000",
          "signers": []
        }
      },
      "lastModifiedLedgerSeq": 1397061
    },
    {
      "keyJson": {
        "trustline": {
          "account_id": "GA2242THTLFWPCW2SF3TTLDWJ3C543UUNFTFIMDJUZYXNW2EMEAXZBRH",
          "asset": {
            "credit_alphanum4": {
              "asset_code": "USDC",
              "issuer": "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
            }
          }
        }
      },
      "dataJson": {
        "trustline": {
          "balance": "12527872975",
          "limit": "9223372036854775807",
          "flags": 1
        }
      },
      "lastModifiedLedgerSeq": 3657583
    }
  ],
  "latestLedger": 4561910
}
```

Both responses describe the same account. Read them side by side:

* Horizon's `native` balance of `9009.2998203` is the account entry's `balance` of `90092998203` stroops.
* Horizon's USDC balance of `1252.7872975` is the trustline entry's `balance` of `12527872975` stroops. It is a separate entry, so it needs a separate key.
* Horizon's `limit` of `922337203685.4775807` is the trustline entry's `limit` of `9223372036854775807`, the largest value a 64-bit amount can hold.
* The entry's four-byte `thresholds` string is `[weight of master|low|medium|high]`, so `"01000000"` means a master key weight of `1` and no other threshold set. Horizon's `thresholds` object exposes only the last three bytes, as `low_threshold`, `med_threshold`, and `high_threshold`.
* The first byte, the master weight, appears in Horizon as the `weight` of the master key in the `signers` array. The raw account entry's `signers` list never includes the master key.
* Horizon's `flags` booleans expand the entry's `flags` bitmask. The trustline's `flags` value of `1` is `AUTHORIZED_FLAG`, which Horizon reports as `is_authorized`.

> [!NOTE]
>
> Pass `"xdrFormat": "json"` to read an entry without an SDK, as the responses above do. Do not build an application on that JSON. The \[`getLedgerEntries`] specification warns that its shape changes whenever the underlying XDR changes. Decode the default base64 XDR with one of the \[SDKs] instead.

### Amounts Are Raw Integers

Every classic amount on the ledger is a signed 64-bit integer of stroops. Horizon divides it by ten million and returns a string with seven decimal places. RPC returns the stroop count itself. It is a JSON string, not a JSON number, because a 64-bit integer does not fit a JSON number safely. Divide it in your own code, and use a big-number type so you do not lose precision. See [Amount precision](https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures/assets.md#amount-precision).

### A Missing Entry Is Not an Error

Horizon answers `404` when a resource does not exist. RPC answers `200` and leaves the key out of `entries`, so a request for two keys can return one entry. If no key exists, `entries` is an empty array. The current server always sends the field, but the [`getLedgerEntries`] specification lists only `latestLedger` as required, so treat a missing `entries` as empty.

Match each returned entry back to its own key with the entry's `keyJson` field, or `key` in the default base64 format. Do not match on the position you sent it in.

[CAP-67]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md

[`AccountEntry`]: https://github.com/stellar/stellar-xdr/blob/v28.0/Stellar-ledger-entries.x#L190

[Horizon]: https://developers.stellar.org/docs/data/apis/horizon

[RPC]: https://developers.stellar.org/docs/data/apis/rpc

[Horizon's REST-like API]: https://developers.stellar.org/docs/data/apis/horizon/api-reference

[Horizon's Response Format]: https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/response-format.md

[RPC JSON-RPC API]: https://developers.stellar.org/docs/data/apis/rpc/api-reference

[JSON-RPC]: https://developers.stellar.org/docs/data/apis/rpc/api-reference/structure/json-rpc.md

[Data]: https://developers.stellar.org/docs/data/analytics

[SDKs]: https://developers.stellar.org/docs/tools/sdks

[`GET /`]: /docs/data/apis/horizon/api-reference

[`GET /ledgers`]: /docs/data/apis/horizon/api-reference/list-all-ledgers

[`GET /ledgers/{seq}`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledger

[`GET /ledgers/{seq}/transactions`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions

[`GET /ledgers/{seq}/operations`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledgers-operations

[`GET /ledgers/{seq}/payments`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledgers-payments

[`GET /ledgers/{seq}/effects`]: /docs/data/apis/horizon/api-reference/retrieve-a-ledgers-effects

[`POST /transactions`]: /docs/data/apis/horizon/api-reference/submit-a-transaction

[`POST /transactions_async`]: /docs/data/apis/horizon/api-reference/submit-async-transaction

[`GET /transactions`]: /docs/data/apis/horizon/api-reference/list-all-transactions

[`GET /transactions/{hash}`]: /docs/data/apis/horizon/api-reference/retrieve-a-transaction

[`GET /transactions/{hash}/operations`]: /docs/data/apis/horizon/api-reference/retrieve-a-transactions-operations

[`GET /transactions/{hash}/payments`]: /docs/data/apis/horizon/api-reference/retrieve-a-transactions-payments

[`GET /transactions/{hash}/effects`]: /docs/data/apis/horizon/api-reference/retrieve-a-transactions-effects

[`GET /operations`]: /docs/data/apis/horizon/api-reference/list-all-operations

[`GET /operations/{id}`]: /docs/data/apis/horizon/api-reference/retrieve-an-operation

[`GET /operations/{id}/effects`]: /docs/data/apis/horizon/api-reference/retrieve-an-operations-effects

[`GET /fee_stats`]: /docs/data/apis/horizon/api-reference

[`GET /accounts`]: /docs/data/apis/horizon/api-reference/list-all-accounts

[`GET /accounts/{address}`]: /docs/data/apis/horizon/api-reference/retrieve-an-account

[`GET /claimable_balances`]: /docs/data/apis/horizon/api-reference/list-all-claimable-balances

[`GET /claimable_balances/{id}`]: /docs/data/apis/horizon/api-reference/retrieve-a-claimable-balance

[`GET /claimable_balances/{id}/transactions`]: /docs/data/apis/horizon/api-reference/cb-retrieve-related-transactions

[`GET /claimable_balances/{id}/operations`]: /docs/data/apis/horizon/api-reference/cb-retrieve-related-operations

[`GET /liquidity_pools`]: /docs/data/apis/horizon/api-reference/list-liquidity-pools

[`GET /liquidity_pools/{id}`]: /docs/data/apis/horizon/api-reference/retrieve-a-liquidity-pool

[`GET /liquidity_pools/{id}/transactions`]: /docs/data/apis/horizon/api-reference/lp-retrieve-related-transactions

[`GET /liquidity_pools/{id}/operations`]: /docs/data/apis/horizon/api-reference/lp-retrieve-related-operations

[`GET /liquidity_pools/{id}/effects`]: /docs/data/apis/horizon/api-reference/retrieve-related-effects

[`GET /liquidity_pools/{id}/trades`]: /docs/data/apis/horizon/api-reference/retrieve-related-trades

[`GET /offers`]: /docs/data/apis/horizon/api-reference/get-all-offers

[`GET /offers/{id}`]: /docs/data/apis/horizon/api-reference/get-offer-by-offer-id

[`GET /offers/{id}/trades`]: /docs/data/apis/horizon/api-reference/get-trades-by-offer-id

[`GET /payments`]: /docs/data/apis/horizon/api-reference/list-all-payments

[`GET /effects`]: /docs/data/apis/horizon/api-reference/list-all-effects

[`GET /trades`]: /docs/data/apis/horizon/api-reference/get-all-trades

[`getLatestLedger`]: ./rpc/api-reference/methods/getLatestLedger

[`getVersionInfo`]: ./rpc/api-reference/methods/getVersionInfo

[`getHealth`]: ./rpc/api-reference/methods/getHealth

[`getNetwork`]: ./rpc/api-reference/methods/getNetwork

[`getLedgers`]: ./rpc/api-reference/methods/getLedgers

[`getTransactions`]: ./rpc/api-reference/methods/getTransactions

[`getTransaction`]: ./rpc/api-reference/methods/getTransaction

[`getEvents`]: ./rpc/api-reference/methods/getEvents

[`sendTransaction`]: ./rpc/api-reference/methods/sendTransaction

[`getFeeStats`]: ./rpc/api-reference/methods/getFeeStats

[`simulateTransaction`]: ./rpc/api-reference/methods/simulateTransaction

[`getLedgerEntries`]: ./rpc/api-reference/methods/getLedgerEntries