slightly different endpoint route (/nft/orders/... instead of /ft/orders/... )
makerAssetType and takerAssetType fields are required
makerAsset and takerAsset contain not plain token addresses, but token address and token type encoded as described in Body parameters
takerAssetId and makerAssetId will contain NFT tokenId . If it's "NFT to fungible" order, takerAssetId = 0 and makerAssetId = tokenID. If it's "fungible to NFT", then the opposite.
makerAsset and takerAsset needs to be encode as packed field containing address of an ERC20/721/1155 token that maker want to sell to the taker (between 0-19 bits). Token type encoded as show above on 20-21 bits.
Example encoding in JavaScript:
Response
Understand the response by checking our dedicated page: