# Event HTTP API and cross-origin

**URL:** <https://community.hubspot.com/t/event-http-api-and-cross-origin/18210>\
**Category:** APIs & Integrations\
**Tags:** events\
**Created:** [January 20, 2020, 7:32am UTC](https://community.hubspot.com/t/event-http-api-and-cross-origin/18210 "2020-01-20T07:32:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Voyager2](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/voyager2/32/18373_2.png) [@Voyager2](https://community.hubspot.com/u/Voyager2)\
**Post date:** [January 20, 2020, 7:32am UTC](https://community.hubspot.com/t/event-http-api-and-cross-origin/18210/1 "2020-01-20T07:32:19Z")

</div>

Is there a way to resolve CORS issues for HubSpot Events HTTP API? I need to allow that for several origins. Only portalId is sent there in the URL - does not look like secret information.

Although such events are accepted by the hubspot server but I would like to avoid CORS warnings

---

<div class="post-metadata">

**Author:** ![Willson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/willson/32/84663_2.png) [@Willson](https://community.hubspot.com/u/Willson)\
**Post date:** [January 20, 2020, 9:23am UTC](https://community.hubspot.com/t/event-http-api-and-cross-origin/18210/2 "2020-01-20T09:23:15Z")

</div>

Hi @Voyager2

I can see that this question was asked on a previous thread where we addressed a CORS question. I’ll go ahead and update that thread so that users with a similar question to this are redirected here.

To look into this for you, would you be able to provide a screenshot of the specific error you’re seeing from your end when using the [Events HTTP API](https://developers.hubspot.com/docs/methods/enterprise_events/http_api)?

---

<div class="post-metadata">

**Author:** ![Voyager2](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/voyager2/32/18373_2.png) [@Voyager2](https://community.hubspot.com/u/Voyager2)\
**Post date:** [January 20, 2020, 3:15pm UTC](https://community.hubspot.com/t/event-http-api-and-cross-origin/18210/3 "2020-01-20T15:15:23Z")

</div>

![console.jpg](https://d2qpr2jzcazej7.cloudfront.net/original/3X/8/2/828209088b990d0f7932899a0efdbc44c2ef5d88.jpeg)

@Willson ,This is the screen. Just usual CORS warning. No CORS headers in the response. It would be good if it is possible to setup a bunch of origins in the HubSpot accont to allow CORS headers for them.

It is not very convenient to proxy such requests with user’s server to avoid warnings.

---

<div class="post-metadata">

**Author:** ![Voyager2](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/voyager2/32/18373_2.png) [@Voyager2](https://community.hubspot.com/u/Voyager2)\
**Post date:** [February 1, 2020, 9:51am UTC](https://community.hubspot.com/t/event-http-api-and-cross-origin/18210/4 "2020-02-01T09:51:02Z")

</div>

Well, no reply. I’ve just made a server-side proxy for these requests.