Skip to content

Conversation

bitkeep-tech
Copy link
Contributor

Fix bitgetwallet endpoint ,
And
Can you provide the IP of the defilama server? Due to the adjustment of our security policy, we need to add the IP to our whitelist. If you cannot provide the IP, we will look at other solutions.

@llamabutler
Copy link

The bitgetwallet adapter exports:

> [email protected] test
> ts-node --transpile-only cli/testAdapter.ts aggregators bitgetwallet

🦙 Running BITGETWALLET adapter 🦙
---------------------------------------------------
Start Date:	Tue, 26 Aug 2025 00:00:00 GMT
End Date:	Wed, 27 Aug 2025 00:00:00 GMT
---------------------------------------------------

[Error: Request failed with status code 403] {
  url: 'https://api-3rd.bitkeep.com/swap-go/open/getOrderDayVolume?chain=sui',
  method: 'GET',
  axiosError: 'Forbidden',
  chain: 'sui'
}

@llamabutler
Copy link

The bitgetwallet adapter exports:

> [email protected] test
> ts-node --transpile-only cli/testAdapter.ts bridge-aggregators bitgetwallet

🦙 Running BITGETWALLET adapter 🦙
---------------------------------------------------
Start Date:	Tue, 26 Aug 2025 00:00:00 GMT
End Date:	Wed, 27 Aug 2025 00:00:00 GMT
---------------------------------------------------

[Error: Request failed with status code 403] {
  url: 'https://api-3rd.bitkeep.com/swap-go/open/getOrderDayVolume?bridge=1&chain=linea&timestamp=1756166400',
  method: 'GET',
  axiosError: 'Forbidden',
  chain: 'linea'
}

@treeoflife2 treeoflife2 self-assigned this Aug 27, 2025
@treeoflife2
Copy link
Member

@bitkeep-tech please can we have alternate solution, as ip keeps changing so we can't rely on that, can we have private api-key or some other way?

@bitkeep-tech
Copy link
Contributor Author

please can we have alternate solution, as ip keeps changing so we can't rely on that, can we have private api-key or some other way?

Understood. I'll confirm this with our team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants