# API exposure in order to allow add\*

**URL:** <https://discuss.ipfs.tech/t/api-exposure-in-order-to-allow-add/4941>\
**Category:** Kubo\
**Created:** [February 27, 2019, 9:52pm UTC](https://discuss.ipfs.tech/t/api-exposure-in-order-to-allow-add/4941 "2019-02-27T21:52:06Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\
**Post date:** [February 27, 2019, 11:31pm UTC](https://discuss.ipfs.tech/t/api-exposure-in-order-to-allow-add/4941/2 "2019-02-27T23:31:57Z")

</div>

You can expose parts of the API with Nginx or any other reverse proxy sitting in front of the IPFS API.

Also, since you can run js-ipfs directly in the browser, you can probably use it to add content to the network.

Also, [IPFS Cluster](https://github.com/ipfs/ipfs-cluster) has an API which supports basic authentication (permissioned endpoints coming up soon as well). Cluster might be interesting even with a single peer because of some API features, like attaching names to pins, or any custom metadata.

---

_[View the full topic](https://discuss.ipfs.tech/t/api-exposure-in-order-to-allow-add/4941)._