Skip to content


We are looking for publications that demonstrate building dApps or smart contracts!
See the full list of Gitcoin bounties that are eligible for rewards.


This guide explains how to search the Algorand Blockchain using the Indexer. This Indexer is not part of the Algorand node and requires a separate binary download. See the Indexer Install Guide for instructions on installing and configuring the new Indexer.

Block Proposal

Algorand V2 Indexer

The primary purpose of this Indexer is to provide a REST API interface of API calls to support searching the Algorand Blockchain. The Indexer REST APIs retrieve the blockchain data from a PostgreSQL compatible database that must be populated. This database is populated using the same indexer instance or a separate instance of the indexer which must connect to the algod process of a running Algorand node to read block data. This node must also be an Archival node to make searching the entire blockchain possible.

The Indexer provides a set of REST API calls for searching blockchain Transactions, Accounts, Assets and Blocks. Each of these calls also provides several filter parameters to support refining searches. The latest Algorand native SDKs (Python, JavaScript, Go, and Java) provide similar functionality. These REST calls are based on the Open API specification and are described in the REST SDK reference documentation.

See the full description of endpoints available in the indexer docs.

SDK client instantiations

const indexerToken = 'a'.repeat(64);
const indexerServer = 'http://localhost';
const indexerPort = 8980;

const indexerClient = new algosdk.Indexer(
Snippet Source

# instantiate indexer client
indexer_host = "http://localhost:8980"
indexer_token = "a" * 64
indexer_client = indexer.IndexerClient(
    indexer_token=indexer_token, indexer_address=indexer_host
Snippet Source

String indexerHost = "http://localhost";
int indexerPort = 8980;
String indexerToken = "a".repeat(64);
IndexerClient indexerClient = new IndexerClient(indexerHost, indexerPort, indexerToken);
Snippet Source

// Create a new indexer client, configured to connect to out local sandbox
var indexerAddress = "http://localhost:8980"
var indexerToken = strings.Repeat("a", 64)
indexerClient, _ := indexer.MakeClient(

// Or, if necessary, pass alternate headers

var indexerHeader common.Header
indexerHeader.Key = "X-API-Key"
indexerHeader.Value = indexerToken
indexerClientWithHeaders, err := indexer.MakeClientWithHeaders(
Snippet Source


When using cURL be aware that the parameters may need to be URL encoded. The SDKs handle the encoding of parameter data.

The indexer provides two primary ways to access information:

1) Lookup a single item (a single account, a single transaction, a single block)

2) Search for items that match a query (transactions for > 100A and between round N and M)

Each SDK provides methods for looking up or searching for transactions, assets, applications(smart contracts), and blocks. For a full list of method calls see the SDK docs:


As an example, to get the details of a specific asset the indexer provides the /assets/{asset-id} REST call. This call takes no parameters as the asset id is passed in the URL. This call returns the details of the asset and the round the results were calculated in.

const indexer = getLocalIndexerClient();
const indexerAssetInfo = await indexer.lookupAssetByID(assetIndex).do();
console.log('Indexer Asset Info:', indexerAssetInfo);
Snippet Source

# lookup a single asset
# by passing include_all, we specify that we want to see deleted assets as well
response = indexer_client.asset_info(asset_id, include_all=True)
print(f"Asset Info: {json.dumps(response, indent=2,)}")
Snippet Source

Long asaId = 25l;
Response<AssetResponse> assetResponse = indexerClient.lookupAssetByID(asaId).execute();
Asset assetInfo = assetResponse.body().asset;
System.out.printf("Name for %d: %s\n", asaId,;
Snippet Source

// query parameters
var assetId uint64 = 2044572
var minBalance uint64 = 50

// Lookup accounts with minimum balance of asset
assetResult, _ := indexerClient.

// Print the results
assetJson, _ := json.MarshalIndent(assetResult, "", "\t")
fmt.Printf(string(assetJson) + "\n")
Snippet Source

$ curl "localhost:8980/v2/assets/2044572" 

Searching is similar to lookup with the ability to return multiple or filtered results. This example searches for transactions based on a few filters.

const transactionInfo = await indexerClient
console.log( =>;
Snippet Source

response = indexer_client.search_transactions(
    min_amount=10, min_round=1000, max_round=1500
print(f"Transaction results: {json.dumps(response, indent=2)}")
Snippet Source

Response<TransactionsResponse> transactionSearchResult = indexerClient.searchForTransactions()
TransactionsResponse txResp = transactionSearchResult.body();
System.out.printf("Found %d transactions that match criteria\n", txResp.transactions.size());
Snippet Source

// query parameters
var transactionMinAmount uint64 = 10

// Query
transactionResult, _ := indexerClient.

// Print results
transactionJson, _ := json.MarshalIndent(transactionResult, "", "\t")
fmt.Printf(string(transactionJson) + "\n")
Snippet Source

$ curl "localhost:8980/v2/transactions?currency-greater-than=10"


When searching large amounts of blockchain data often the results may be too large to process in one given operation. In fact, the indexer imposes hard limits on the number of results returned for specific searches. The default limits for these searches are summarized in the table below.

Search Type Maximum number of results per search
API Resources Per Account 1,000
Transactions Search 1,000
Accounts Search 100
Assets Search 100
Balances Search 1,000
Applications Search 100

When trying to find specific transactions, the Indexer supplies a pagination method that allows separating the results into several REST calls to return larger result sets. When used with the limit parameter the results for large data sets can be returned in expected result counts.

For example, adding a limit parameter of 5 to the previous call will cause only 5 results to be returned in each page. To get the next 5 transactions simply add the next-token as a parameter to the next REST call. The parameter is named next and this token is only good for the next 5 results.

let nextToken = '';

// nextToken will be undefined if we reached the last page
while (nextToken !== undefined) {
  // eslint-disable-next-line no-await-in-loop
  const response = await indexerClient

  nextToken = response['next-token'];
  const txns = response.transactions;
  if (txns.length > 0)
    console.log(`Transaction IDs: ${ =>}`);
Snippet Source

nexttoken = ""
has_results = True
page = 0

# loop using next_page to paginate until there are
# no more transactions in the response
while has_results:
    response = indexer_client.search_transactions(
        min_amount=10, min_round=1000, max_round=1500, next_page=nexttoken

    has_results = len(response["transactions"]) > 0

    if has_results:
        nexttoken = response["next-token"]
        print(f"Tranastion on page {page}: " + json.dumps(response, indent=2))

    page += 1
Snippet Source

String nextToken = "";
boolean hasResults = true;
// Start with empty nextToken and while there are
// results in the transaction results, query again with the next page
while (hasResults) {
    Response<TransactionsResponse> searchResults = indexerClient.searchForTransactions().minRound(1000l)
    TransactionsResponse txnRes = searchResults.body();
    // ... do something with transaction results
    hasResults = txnRes.transactions.size() > 0;
    nextToken = txnRes.nextToken;
Snippet Source

var nextToken = ""
var numTx = 1
var numPages = 1
var pagedMinAmount uint64 = 10
var limit uint64 = 1

for numTx > 0 {
    // Query
    pagedResults, err := indexerClient.
    if err != nil {
    pagedTransactions := pagedResults.Transactions
    numTx = len(pagedTransactions)
    nextToken = pagedResults.NextToken

    if numTx > 0 {
        // Print results
        pagedJson, err := json.MarshalIndent(pagedTransactions, "", "\t")
        if err != nil {
        fmt.Printf(string(pagedJson) + "\n")
        fmt.Println("End of page : ", numPages)
        fmt.Println("Transaction printed : ", len(pagedTransactions))
        fmt.Println("Next Token : ", nextToken)
Snippet Source

$ curl "localhost:8980/v2/transactions?currency-greater-than=10&limit=5"
# note the "next-token" field in the most recent results and supply the value to the "next" parameter
$ curl "localhost:8979/v2/transactions?currency-greater-than=10&limit=5&next=cAoBAAAAAAAAAAAA"

Results showing "next-token"

   "next-token" : "cAoBAAAAAAAAAAAA",
   "current-round" : 7050272,
   "transactions" : []

A new next token will be returned to get the next five. This token acts as a marker in the current result set and allows the next call to pick up where the last search ended. We note that the 'limit' parameter can also be used to specify a larger (rather than smaller) results set than the defaults above. These limits are shown in the following table and are per call, not the total result set.

Search Type Search Limit with a limit parameter
Transaction Search 10000
Account Search 1000
Asset Search 1000
Asset Balance Search 10000

The following REST calls support paginated results.

  • /accounts - Search for specific accounts.
  • /accounts/{account-id}/transactions - Search for transactions for a specific account.
  • /accounts/{account-id}/created-apps - Search for created applications for a specific account.
  • /accounts/{account-id}/created-assets - Search for created assets for a specific account.
  • /accounts/{account-id}/assets - Search for assets on a specific account.
  • /accounts/{account-id}/apps-local-state - Search for application local state for a specific account.
  • /assets - Search Assets.
  • /assets/{asset-id}/balances - Search Asset balances.
  • /assets/{asset-id}/transactions - Search for Transactions with a specific Asset.
  • /transactions - Search all transactions

Note field searching

Every transaction has the ability to add up to a 1kb note in the note field. Several of the REST APIs provide the ability to search for a prefix that is present in the note field, meaning that the note starts with a specific string. This can be a very powerful way to quickly locate transactions that are specific to an application. The REST calls that support prefix searching are the following.

  • /accounts/{account-id}/transactions - Search for a prefix for a specific accounts transactions.
  • /assets/{asset-id}/transactions - Search for a prefix for a specific Asset Id.
  • /transactions - Search all Transactions for a specific transaction note field prefix.

To search for a specific prefix use the note-prefix parameter. For the Javascript and direct REST API, the value needs to be base64 encoded to return results. (The other SDKs perform the base64 encoding for you.) For example, if the contents of the note field started with the string “showing prefix searches”, encoding the beginning of that sentence using python like the following:

$ python3 -c "import base64;print(base64.b64encode('showing prefix'.encode()))"

This will return an encoded value of c2hvd2luZyBwcmVmaXg=. This value can then be passed to the search. To search all transactions use the following command.

const txnsWithNotePrefix = await indexerClient
  `Transactions with note prefix "Hello" ${JSON.stringify(
Snippet Source

note_prefix = "showing prefix".encode()
response = indexer_client.search_transactions(note_prefix=note_prefix)
print(f"result: {json.dumps(response, indent=2)}")
Snippet Source

byte[] prefix = new String("showing prefix").getBytes();
Response<TransactionsResponse> prefixResults = indexerClient.searchForTransactions().notePrefix(prefix)
// ...
Snippet Source

// Parameters
var notePrefix = "showing prefix"

// Query
prefixResult, _ := indexerClient.

// Print results
prefixJson, _ := json.MarshalIndent(prefixResult, "", "\t")
fmt.Printf(string(prefixJson) + "\n")
Snippet Source

python3 -c "import base64;print(base64.b64encode('showing prefix'.encode()))"
$ curl "localhost:8980/v2/transactions?note-prefix=c2hvd2luZyBwcmVmaXg=" | json_pp