For the complete documentation index, see llms.txt. This page is also available as Markdown.

Litecoin

GetBlock provides RPC endpoints that implement the Litecoin JSON-RPC API standard. These methods are core functionalities for interacting with Litecoin nodes.

The Litecoin network offers a comprehensive suite of methods that enable developers to interact seamlessly with its blockchain infrastructure. This overview provides an in-depth examination of these methods, categorizing them into key functional areas for better understanding and implementation.

What you can expect to find in this documentation

  • Compatibility with the Litecoin mainnet and testnets

  • Purpose, functionality, and use cases of each Litecoin method

  • Required input parameters

  • Sample requests and responses

  • Code examples in multiple programming languages (Python, JavaScript)

What you can do with this API:

  • Query real-time blockchain data

  • Retrieve block and transaction information

  • Monitor mempool and network status

  • Submit and track transactions

  • Access mining statistics and difficulty

TECHNICAL DISCLAIMER: AUTHORITATIVE JSON-RPC API SPECIFICATION.

GetBlock's RPC API reference documentation is provided exclusively for informational purposes and streamlined developer experience optimization. The canonical and normative specification for Litecoin JSON-RPC methods is solely maintained and published through the official Litecoin Core documentation.

Base URL

Supported Networks

Network
JSON RPC
Blockbook (REST)
Blockbook (WebSocket)

Mainnet

✅

✅

✅

JSON-RPC is the Litecoin Core node interface. Blockbook is a separate add-on providing an address- and xpub-indexed view of the chain, and its REST and WebSocket interfaces are provisioned as their own endpoints with their own URLs. A JSON-RPC endpoint does not answer address, UTXO, or wallet queries, and the Litecoin Core wallet RPCs such as listunspent are disabled on shared nodes. See the Blockbook add-on.

Interface
Use it for

Node-level queries: blocks, raw transactions, mempool, mining, network state

Address balances, UTXOs, wallet-level xpub queries, transaction history, fiat rates

The same queries plus live subscriptions to new blocks and address activity

Quickstart

In this section, you will learn how to make your first call with either:

  • Axios

  • Python

Before you begin, you must have already installed npm or yarn on your local machine (for the Axios example) or Python and pip (for the Python example).

1

Setup project

Create and initialize a new project:

2

Install Axios

3

Create file

Create a new file named index.js. This is where you will make your first call.

4

Set ES module type

Set the ES module "type": "module" in your package.json.

5

Add code

Add the following code to index.js:

Replace <ACCESS-TOKEN> with your actual access token from GetBlock.

6

Run the script

Expected output (example):

1

Setup the project directory

2

Create and activate a virtual environment

3

Install requests

4

Create script

Create a file called main.py with the following content:

Replace <ACCESS-TOKEN> with your actual access token from GetBlock.

5

Run the script

Available Methods

Litecoin is documented across three interfaces, each provisioned as its own endpoint.

  1. Litecoin JSON-RPC API: The Litecoin Core node interface: blocks, raw transactions, mempool inspection, mining data, network state, and fee estimation. Methods are grouped by area on the section page.

  2. Litecoin Blockbook REST API: Address- and xpub-indexed queries over HTTP: balances, transaction history, unspent outputs, wallet-level xpub lookups, balance history, and fiat rates.

  3. Litecoin Blockbook (WebSocket) API: The same indexed queries over a persistent connection, plus subscriptions to new blocks and to activity on a set of addresses.

A JSON-RPC endpoint has no address index, so address balances and UTXO lookups belong on Blockbook. The Litecoin Core wallet RPCs, including listunspent, are disabled on shared nodes because those nodes carry no user wallets.

Support

For technical support and questions:

See Also

Last updated

Was this helpful?