# Usage of api.segment.io in streamlit

**URL:** <https://discuss.streamlit.io/t/usage-of-api-segment-io-in-streamlit/43899>\
**Category:** Using Streamlit\
**Created:** [May 24, 2023, 7:34am UTC](https://discuss.streamlit.io/t/usage-of-api-segment-io-in-streamlit/43899 "2023-05-24T07:34:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike12](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@Mike12](https://discuss.streamlit.io/u/Mike12)\
**Post date:** [May 24, 2023, 7:34am UTC](https://discuss.streamlit.io/t/usage-of-api-segment-io-in-streamlit/43899/1 "2023-05-24T07:34:55Z")

</div>

We have CORS misconfiguration issue identified in our application that is using streamlit library. The application is not vulnerable to any other request except the API endpoint [https://api.segment.io/](https://api.segment.io/). We tried to fix the CORS issue by adding different domains. However the issue still persists. Can we remove this endpoint if it is not important?

Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/streamlit/original/3X/c/f/cf4c2ee0d938358f82448c5fe4b9c3c91d7ce19c.svg) [@system](https://discuss.streamlit.io/u/system)\
**Post date:** [November 20, 2023, 7:35am UTC](https://discuss.streamlit.io/t/usage-of-api-segment-io-in-streamlit/43899/2 "2023-11-20T07:35:26Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
