# Switch API

**URL:** <https://forum.interledger.org/t/switch-api/479>\
**Category:** Applications and Use Cases\
**Created:** [April 5, 2019, 4:51pm UTC](https://forum.interledger.org/t/switch-api/479 "2019-04-05T16:51:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lucian\_Trestioreanu](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/lucian_trestioreanu/32/186_2.png) [@Lucian\_Trestioreanu](https://forum.interledger.org/u/Lucian_Trestioreanu)\
**Post date:** [April 5, 2019, 4:51pm UTC](https://forum.interledger.org/t/switch-api/479/1 "2019-04-05T16:51:19Z")

</div>

This was originally a question regarding Switch API setup, but because in the mean time I solved it, I thought I would turn this post into something useful for the community. - a few tips:

- credentials in small caps - at least ETH

- when it runs it creates a config file in home/user/.switch. If run multiple times with same credentials (tests), this file has to be deleted first

- in some cases, the response from the network regarding the validated ledger might take a little bit to arrive. In this case, a tx request would not receive the correct answer; work around is to introduce a delay for the tx request, as in [here](https://forum.interledger.org/t/interoperability-prototype-with-moneyd/382/14).  
This has to be done also on the reference connector side, in the @kava xrp-plugin.

- below is the config of the reference ilp connector to connect to Switch Api, in case [@kava connector-config](https://github.com/kava-labs/connector-config) is not used. While for the given use case it wasn’t needed, in a real scenario, for “outgoingChannelAmount”, “minIncomingChannelAmount”, “maxPacketAmount”, you may still want to use a conversion as in @kava’s original connector-config.

---

<div class="post-metadata">

**Author:** ![kincaid](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/kincaid/32/39_2.png) [@kincaid](https://forum.interledger.org/u/kincaid)\
**Post date:** [April 16, 2019, 11:26pm UTC](https://forum.interledger.org/t/switch-api/479/3 "2019-04-16T23:26:29Z")

</div>

Hey @Lucian_Trestioreanu!

Thanks again for test driving it!

Some updates based on your feedback:

- Fingers crossed, we fixed the issue you experienced with the XRP NotFoundError in v0.4.3+ of @kava-labs/ilp-plugin-xrp-paychan and v0.4.7+ of @kava-labs/switch-api
- Added a note to the README in ilp-sdk (renamed switch-api) explaining the config file and where it’s located 👍

---

<div class="post-metadata">

**Author:** ![Lucian\_Trestioreanu](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/lucian_trestioreanu/32/186_2.png) [@Lucian\_Trestioreanu](https://forum.interledger.org/u/Lucian_Trestioreanu)\
**Post date:** [April 17, 2019, 8:42am UTC](https://forum.interledger.org/t/switch-api/479/4 "2019-04-17T08:42:53Z")

</div>

Hi, @Kincaid! 🙂 Thank you very much for your hints towards unblocking the issue, and for this quick update! Congrats Kava for Switch API!

---

<div class="post-metadata">

**Author:** ![Lucian\_Trestioreanu](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/lucian_trestioreanu/32/186_2.png) [@Lucian\_Trestioreanu](https://forum.interledger.org/u/Lucian_Trestioreanu)\
**Post date:** [May 8, 2019, 11:05am UTC](https://forum.interledger.org/t/switch-api/479/5 "2019-05-08T11:05:09Z")

</div>

Hi, @Kincaid!

ILP-SDK can at this point swap currencies for same user, is this correct?  
How about using it to send ETH from user A towards user B XRP wallet?

i.e., instead entering user A private key ETH (sending wallet) + user A private key XRP (receiving wallet),  
to fill in: user A private key ETH (sending wallet) + user B XRP address (receiving wallet)?

Generally, does anybody know if there is any working app (way) able to send XRP from User A’s XRP wallet towards User B’s ETH wallet right now?

Thank you very much