feat: tokens route for getting IDs #177
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

TL;DR
Added a new API endpoint to retrieve token IDs by type for a specific contract address.
What changed?
GET /{chainId}/tokens/{address}to retrieve token IDs by type (ERC721 or ERC1155) for a specific token addressTokenIdModelstruct to represent token ID data in the responsetoken_typefrom path to query parameter)How to test?
/{chainId}/tokens/{address}with the following parameters:token_type: Optional filter for token type (erc721 or erc1155)hide_zero_balances: Boolean to filter out zero balancespageandlimit: For paginationWhy make this change?
This endpoint allows clients to retrieve all token IDs for a specific token contract address, which is useful for applications that need to display or work with all tokens from a particular collection. The endpoint complements the existing token holders endpoint by providing a different view of the token data.