V1 `defi.getPairAddress` returning 404 for some pairs

Moralis General
#1

Testing defi.getPairAddress with the following input:

{"token0_address":"0x77f9CF0bd8C500CfFdF420e72343893aeCC2EC0b","token1_address":"0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2","exchange":"uniswapv2","chain":"eth"}

I receive a 404 error from the API:

  Error: {"message":"Request failed with status code 404","code":141}

Iā€™m not sure if this is due to ā€œreverse pair tokensā€ or some other ā€œnon-standardā€ feature.

Is there any way we can get more detailed failure feedback?

#2

Iā€™ll have to check, it may be an issue on our side related to the exchange parameter.

#3

we will have to investigate more to see what happens, I get the same result as you had

#4

For what itā€™s worth, this appears to be a recent development. Iā€™ve acquired this pair before. Not sure if it was a V1 to V2 ā€œinfrastructureā€ issue or anything.

Iā€™ve got an app demo this week, so definitely interested in getting this resolved rather than having to put together a more ā€œmanualā€ method. šŸ« 

Thanks.

#5

you can try again now