[BUG] Cannot get price

Question

[BUG] Cannot get price

0xMarsRover opened this issue 2 years ago · 10 comments

Hi,

I used two scripts below for getting prices of nfts, but all failed. I remembered that I can get prices by using function "offers" or "offersByUrl" before, but they do not work now.
Script 1:
let result_testnet = await OpenseaScraper.offersByUrl("https://testnets.opensea.io/collection/doodles-officias", options); console.dir(result_testnet, {depth: null}); // result object contains keys stats and offers

Script 2:
let result = await OpenseaScraper.offers(nft, options); console.dir(result, {depth: null}); // result object contains keys stats and offers

Any suggestions for that? Thanks.

Answer 1 · 2022-07-13T22:23:52.000Z

thanks a lot, its a bug, working on it.

Answer 2 · 2022-07-13T22:31:43.000Z

Thanks for your response. I think opensea website Could have updates somewhere.

Answer 3 · 2022-07-13T22:59:26.000Z

So opensea changed some variable names in their __wired__ variable (we get the prices from that variable).

I noticed that quantityInEth is not longer availible. Instead only quantity seems to exist.

// doesnt work anymore
Object.values(__wired__.records)
    .filter(o => o.__typename === "AssetQuantityType")
    .filter(o => o.quantityInEth) // ❌ this breaks

// seems to work 
Object.values(__wired__.records)
    .filter(o => o.__typename === "AssetQuantityType")
    .filter(o => o.quantity) // returns something but with wrong mapping

Unfortunately simply chaning this does NOT fix the issue, because the mapping is off. This needs more investigation. Leaving my findings here for now.

Answer 4 · 2022-08-05T09:43:14.000Z

So opensea changed some variable names in their __wired__ variable (we get the prices from that variable).

I noticed that quantityInEth is not longer availible. Instead only quantity seems to exist.
// doesnt work anymore
Object.values(__wired__.records)
    .filter(o => o.__typename === "AssetQuantityType")
    .filter(o => o.quantityInEth) // ❌ this breaks

// seems to work 
Object.values(__wired__.records)
    .filter(o => o.__typename === "AssetQuantityType")
    .filter(o => o.quantity) // returns something but with wrong mapping
Unfortunately simply chaning this does NOT fix the issue, because the mapping is off. This needs more investigation. Leaving my findings here for now.

Is there any updates on this issue? Thanks

Answer 5 · 2022-08-05T10:23:12.000Z

I currently don't have time to fix this. I have it on my todo list, but I cannot promise nor predict any timeline.

Answer 6 · 2022-08-05T10:40:48.000Z

Thnaks for your reply.

I currently don't have time to fix this. I have it on my todo list, but I cannot promise nor predict any timeline.

Answer 7 · 2022-08-16T14:45:05.000Z

I did some investigations on Opensea website abnd made some changes on source code. Now it seems work.

const floorPrices = Object.values(__wired__.records)
  .filter(o => o.__typename === "PriceType" && o.eth && o.unit && o.usd)
  .filter(o => o.eth)
  .map(o => {
    return {
      amount: o.eth,
      currency: 'ETH',
    }
  });

Answer 8 · 2022-08-19T05:48:06.000Z

I did some investigations on Opensea website abnd made some changes on source code. Now it seems work.

const floorPrices = Object.values(__wired__.records) .filter(o => o.__typename === "PriceType" && o.eth && o.unit && o.usd) .filter(o => o.eth) .map(o => { return { amount: o.eth, currency: 'ETH', } });

this works!! thank you!

Answer 9 · 2022-08-19T07:40:09.000Z

thanks @kaiqiangh for the fix! I adapted it in the new version 6.5.2. To adapt please use version 6.5.2:

npm install opensea-scraper@6.5.2

or alternatively if you have it already installed upgrade to latest version

npm upgrade

Thank you! ♥️

Answer 10 · 2022-08-19T09:42:00.000Z

thanks @kaiqiangh for the fix! I adapted it in the new version 6.5.2. To adapt please use version 6.5.2:
npm install opensea-scraper@6.5.2
or alternatively if you have it already installed upgrade to latest version
npm upgrade
Thank you! ♥️

All good! Thanks!