Skip to main content

[Service] 2026-09-22

Posted: September 22, 2026

This update is scheduled on September 29, 2026 (KST)


The response ordering of the Web3 Data API getNftsOwnedByAccount is changing, and the Aptos Indexer API for Testnet is reaching end of support.

Items in getNftsOwnedByAccount are currently ordered by balance and token ID, both in descending order. After the update, items are ordered by balance in descending order, then by token ID and contract address in ascending order.

The Aptos Indexer API, which serves indexed Aptos data over GraphQL, is ending support for Testnet on September 29, 2026 (KST). Applications that query Aptos Testnet data through this API need to move to another interface before that date. Support for Mainnet continues without change.

1. Response Ordering Change for Get NFTs Owned By Account

getNftsOwnedByAccount returns the NFTs held by an account together with the balance of each token. The ordering rule that decides how these items are listed is being refined so that results are consistent within the same balance.

Currently, items are sorted by balance in descending order, and items with the same balance are sorted by tokenId in descending order. After the update, balance remains the primary key in descending order, while items with the same balance are sorted by tokenId in ascending order. The contract address is added as a final key in ascending order, so that items with the same balance and token ID across different contracts are also returned in a deterministic order.

Sort keyAs-IsTo-Be
balanceDescendingDescending
tokenIdDescendingAscending
contract.addressNot appliedAscending (added)

The response schema does not change. Only the order in which items appear in the items array is affected, including the order across pages when using page or cursor pagination.

Affected API and Networks

This update applies to the following API on all networks where it is available.

If your application relies on the order of the items array, for example by assuming that the item with the highest tokenId appears first within the same balance, the position of items in the response will change after the update. Applications that sort the items on their side, or that look up items by tokenId and contract.address, are not affected.

Please review any logic that depends on the response order before September 29, 2026, so that your service is not affected after the update.

Timeline

  • September 22, 2026: Change announced
  • September 29, 2026 (KST): Updated ordering applied

2. End of Support for Aptos Testnet Indexer API

The Aptos Indexer API provides GraphQL access to indexed Aptos data, along with query templates for coin and NFT data. Support for this API is ending on Testnet, while it remains available on Mainnet.

After September 29, 2026 (KST), the Testnet endpoint stops serving GraphQL requests. Requests sent to the Mainnet endpoint are served as before, and the Aptos Indexer API documentation remains published for Mainnet use.

Affected Network

This change applies to the Aptos Indexer API on Testnet only.

NetworkAptos Indexer API
MainnetAvailable, no change
TestnetEnd of support on September 29, 2026 (KST)

The documentation below continues to describe the Mainnet service.

The Aptos Node API, Web3 Data API, and Webhook continue to operate on both Mainnet and Testnet and are not affected by this change.

After the end-of-support date, GraphQL queries sent to the Aptos Testnet Indexer API no longer return data, so development and test environments that depend on it stop receiving Aptos Testnet data. Production workloads on Mainnet are not affected.

Account, token, and NFT data that is commonly retrieved through the Indexer API is also available on Testnet through the Web3 Data API and the Aptos Node API. Review which queries your test environment relies on and replace them with the corresponding API before September 29, 2026.

Timeline

  • September 22, 2026: End of support announced
  • September 29, 2026 (KST): Aptos Testnet Indexer API endpoint retired

If you have any questions about this update, please contact us at [email protected].

Thank you.

Sincerely, Nodit Team