Interactive NFD lookup
If you want to provide interactive search features for an NFD. You can use the NFD 'search' endpoint using the prefix query parameter.
The endpoint is just the /nfd base endpoint. It takes many query parameters but only certain types should be specified at one time.
ie: prefix, but not owner or reservedFor.
get
https://api.nf.domains
/nfd
[DEPRECATED] Search for NFDs based on select lookup criteria
http https://api.nf.domains/nfd?prefix=patric&limit=4
[
{
"name": "patricia.algo",
"properties": {},
"state": "owned"
},
{
"caAlgo": [
"MQ2QJHZSZ6A7ZXPFE2EPIWLYUMRRDO3DQBEO6NIQ2B5A5OJ4VMWOOI2AX4"
],
"depositAccount": "MQ2QJHZSZ6A7ZXPFE2EPIWLYUMRRDO3DQBEO6NIQ2B5A5OJ4VMWOOI2AX4",
"name": "patrick.algo",
"properties": {
"verified": {
"avatar": "ipfs://bafkreidyc2aeaawgztitvkdbo5tguskghthf6isu3ww6a3djnoqccn63k4",
"avatarasaid": "777149941"
}
},
"state": "owned"
},
{
"name": "patrickkaminski.algo",
"properties": {},
"state": "owned"
},
{
"name": "patrickmahomes.algo",
"properties": {},
"state": "forSale"
}
]
The thumbnail view will return verified and userDefined avatars for names. This way, the UI can show avatars with choices as well, as seen here in this NFDomains search UI example:
Note the verified.avatarasaid property in this example (same exists for banner, bannerasaid when fetching with other views). For integrations that manage their own ASA caching, this may make it easier to reference already cached versions of the NFT image if the ASA id is used instead of IPFS CID references.