We try very hard to maintain backward compatibility with our schema but occasionally we need to deprecate some parts to streamline our code base and to make way for new features. We will always try to give as much notice as possible with changes like these. After 1st March 2023 the following parts of our schema will be deprecated and will no longer be supported. Please also note a number of input and response properties have also been changed.
If you have any concerns or queries regarding the changes please feel free to reach out to us through chat or email us at help@bitpandacustody.com and we will be happy to answer any queries you may have. You can also find further information regarding our api here.
Deprecated as of 1st March 2023 (COMPLETED)
The following items in the schema will be deprecate and no longer supported from 1st March 2023, below you can find examples of some of the migrations.
query { user { wallets { items { id # Referenced as walletId in walletsInfo address # subwallet address now has to be retrieved by querying user.subWallets or user.subWallet walletType # walletType exposed through user.subWallets or user.subWallet name # subwallet name exposed through user.subWallets or user.subWallet createdAt # subwallet createdAt exposed through user.subWallets or user.subWallet updatedAt # subwallet updatedAt exposed through user.subWallets or user.subWallet subWalletId { # subWalletId exposed through user.subWallets or user.subWallet as a string (subWalletId) id index type } subWalletIdString # subWalletId exposed through user.subWallets or user.subWallet as a subWalletId } } } }