# CORS issue with API v1.1

**URL:** <https://discuss.circleci.com/t/cors-issue-with-api-v1-1/50924>\
**Category:** API\
**Created:** [May 21, 2024, 3:11pm UTC](https://discuss.circleci.com/t/cors-issue-with-api-v1-1/50924 "2024-05-21T15:11:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![matiusz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/matiusz/32/35158_2.png) [@matiusz](https://discuss.circleci.com/u/matiusz)\
**Post date:** [May 21, 2024, 3:11pm UTC](https://discuss.circleci.com/t/cors-issue-with-api-v1-1/50924/1 "2024-05-21T15:11:24Z")

</div>

Hi,  
I’ve been using API v1.1 for some time to access build artifacts. Up until recently it was working fine, but from sometime around 1 week ago, there seems to be an issue with CORS, namely the reponse is rejected because  
“Reason: CORS header ‘Access-Control-Allow-Origin’ missing”

The example api call is  
./api/v1.1/project/github///879/artifacts  
which is working fine when accessed directly in browser, but when I’m trying to access the same path with a script from another website, there is a CORS error.  
The respose headers are missing “Access-Control-Allow-Origin: \*” definition, so it’s not possible to access data from the API.

---

<div class="post-metadata">

**Author:** ![alvarosantossyngenta](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alvarosantossyngenta/32/35468_2.png) [@alvarosantossyngenta](https://discuss.circleci.com/u/alvarosantossyngenta)\
**Post date:** [August 6, 2024, 10:51am UTC](https://discuss.circleci.com/t/cors-issue-with-api-v1-1/50924/2 "2024-08-06T10:51:09Z")

</div>

@circleci-community, any questions related with CORS have been answered by the company.  
Do you plan to do it??

---

<div class="post-metadata">

**Author:** ![oliviertassinari](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/oliviertassinari/32/16300_2.png) [@oliviertassinari](https://discuss.circleci.com/u/oliviertassinari)\
**Post date:** [August 19, 2024, 1:47pm UTC](https://discuss.circleci.com/t/cors-issue-with-api-v1-1/50924/3 "2024-08-19T13:47:25Z")

</div>

It’s the same issue with the v2.0 of the API, no?

---

<div class="post-metadata">

**Author:** ![matiusz](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/matiusz/32/35158_2.png) [@matiusz](https://discuss.circleci.com/u/matiusz)\
**Post date:** [August 19, 2024, 2:39pm UTC](https://discuss.circleci.com/t/cors-issue-with-api-v1-1/50924/4 "2024-08-19T14:39:30Z")

</div>

Hi, I can reproduce the same issue with v2 API.

---

<div class="post-metadata">

**Author:** ![alvarosantossyngenta](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/alvarosantossyngenta/32/35468_2.png) [@alvarosantossyngenta](https://discuss.circleci.com/u/alvarosantossyngenta)\
**Post date:** [August 20, 2024, 6:06am UTC](https://discuss.circleci.com/t/cors-issue-with-api-v1-1/50924/5 "2024-08-20T06:06:20Z")

</div>

Yeah. It is impossible to use the API from a React app. This is behaviour is not happening for example using Github API.

Besides, Neither is circleci support team (@circleci-community) seen nor is he expected…