---
title: "Comment by Zlati Pehlivanov on \"How to hide your front-end API keys\" | Hashnode"
description: "That all sounds right, for web at least, but most of the services that require api key, actually require from you to enter a domain to which this api key is giv"
url: "https://hashnode.com/posts/how-to-hide-your-front-end-api-keys/5e445ab98c89a92316ccdc6e/comment/5e47f6368c89a92316cd2e15"
---

[Discussion](https://hashnode.com/posts/how-to-hide-your-front-end-api-keys/5e445ab98c89a92316ccdc6e)

Comment [How to hide your front-end API keys](https://hashnode.com/posts/how-to-hide-your-front-end-api-keys/5e445ab98c89a92316ccdc6e)

[Zlati Pehlivanov](https://hashnode.com/@zlatip)

[Feb 15, 2020](https://hashnode.com/posts/how-to-hide-your-front-end-api-keys/5e445ab98c89a92316ccdc6e/comment/5e47f6368c89a92316cd2e15)

That all sounds right, for web at least, but most of the services that require api key, actually require from you to enter a domain to which this api key is given and for mobiles sha1 of your app at least on android. So requests from different domain and from different mobile app will fail. How this proxy makes things better, what about you will have to pay more for that proxy to work non stop for everybody. Why implementing the same authorization twice?

[Mauricio Robayo](https://hashnode.com/@mauriciorobayo)

[Feb 16, 2020](https://hashnode.com/posts/how-to-hide-your-front-end-api-keys/5e445ab98c89a92316ccdc6e/comment/5e47f6368c89a92316cd2e15#reply-5e48a97a8c89a92316cd363d)

Hi, you are right! That's not the use case for what's described. I don't see why would you implement a proxy server if the API service you are using handles credentials authorization with allowed domains. That's stated on the article.
