# How to call the wallet owner\_api remotely

**URL:** <https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252>\
**Category:** Tech Support\
**Created:** [February 25, 2019, 9:29am UTC](https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252 "2019-02-25T09:29:36Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nick](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/nick/32/1752_2.png) [@nick](https://forum.grin.mw/u/nick)\
**Post date:** [February 25, 2019, 9:29am UTC](https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252/1 "2019-02-25T09:29:36Z")

</div>

**# Wallet Sending via API**

Before we can call the following wallet API, we need run a grin wallet listening on owner api  
$ grin wallet owner\_api

From the grin-wallet.log file we can see the following information:  
INFO grin\_wallet::controller - Starting HTTP Owner API server at 127.0.0.1:13420

## Http/s Method

But if I want to remotely call the Wallet Owner API and the Wallet Foreign API on another service machine, how do I configure them?

Otherwise, if the system defaults, only the Wallet Owner API and Wallet Foreign API calls are made on the current server

---

<div class="post-metadata">

**Author:** ![nikito7](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@nikito7](https://forum.grin.mw/u/nikito7)\
**Post date:** [February 25, 2019, 1:17pm UTC](https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252/2 "2019-02-25T13:17:41Z")

</div>

Ssh tunnel

Or change to 0.0.0.0 not recommended

---

<div class="post-metadata">

**Author:** ![nick](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/nick/32/1752_2.png) [@nick](https://forum.grin.mw/u/nick)\
**Post date:** [February 25, 2019, 1:30pm UTC](https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252/3 "2019-02-25T13:30:28Z")

</div>

How to change to 0.0.0.0 ？ I did not find the relevant command operation

---

<div class="post-metadata">

**Author:** ![nikito7](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@nikito7](https://forum.grin.mw/u/nikito7)\
**Post date:** [February 25, 2019, 1:45pm UTC](https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252/4 "2019-02-25T13:45:36Z")

</div>

sorry  
Only possible change  
api\_listen\_interface = “0.0.0.0”  
in grin-wallet.toml

Use ssh port forward

---

<div class="post-metadata">

**Author:** ![nick](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/nick/32/1752_2.png) [@nick](https://forum.grin.mw/u/nick)\
**Post date:** [February 25, 2019, 1:56pm UTC](https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252/5 "2019-02-25T13:56:27Z")

</div>

This is the way tried, but can not, is still 127.0.0.1:13420

---

<div class="post-metadata">

**Author:** ![nikito7](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@nikito7](https://forum.grin.mw/u/nikito7)\
**Post date:** [February 25, 2019, 1:57pm UTC](https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252/6 "2019-02-25T13:57:41Z")

</div>

Maybe some iptables stuff

> <https://unix.stackexchange.com/questions/10428/simple-way-to-create-a-tunnel-from-one-local-port-to-another>

---

<div class="post-metadata">

**Author:** ![cfleeac](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@cfleeac](https://forum.grin.mw/u/cfleeac)\
**Post date:** [March 1, 2019, 10:57am UTC](https://forum.grin.mw/t/how-to-call-the-wallet-owner-api-remotely/4252/7 "2019-03-01T10:57:13Z")

</div>

Sounds dangerous to make the owner\_api service exposed in public. But you can still use **SSH tunnel** to forward your local port to the remote owner\_api.