NFTs endpoint

Nim Siriwardana : CTO of MetaCask
Nim needs a polling mechanism that keeps track of what is happening on-chain. He needs updated data that shows him the current state of his contracts on chain. He presently takes the information coming off of the Casper chain and replicates it into a database. It is valuable to him to have this infrastructure be built and kept up to date by Casper Labs. He is indexing NFT’s in his contracts.

Nim would also like to get a data feed that plugs into ERP systems such as SAP for his customers.

The following endpoints can address his needs:

Endpoint: /contracts/{contract_address}/nfts

Method: GET

Description: This endpoint retrieves information about NFTs within a specific contract. The response should include metadata, ownership details, and other relevant information about the indexed NFTs.

Endpoint: /data-feed

Method: GET

Description: This endpoint provides a data feed suitable for integration with ERP systems like SAP. The data feed should offer a standardized format that can be easily consumed by external systems.

Start by locating the existing API route definitions and the indexed contract and NFT data paths for /contracts/{contract_address}/nfts and /data-feed. Review how Casper chain data is currently exposed, then define completion as the NFT endpoint returning metadata and ownership details and the data feed providing a standardized format for ERP integrations such as SAP.

Written by the indexing model from the issue text.