# Unable to run react example

**URL:** <https://community.bloomreach.com/t/unable-to-run-react-example/988>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [April 18, 2019, 11:33am UTC](https://community.bloomreach.com/t/unable-to-run-react-example/988 "2019-04-18T11:33:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SathishKannan](https://avatars.discourse-cdn.com/v4/letter/s/6a8cbe/32.png) [@SathishKannan](https://community.bloomreach.com/u/SathishKannan)\
**Post date:** [April 18, 2019, 11:33am UTC](https://community.bloomreach.com/t/unable-to-run-react-example/988/1 "2019-04-18T11:33:09Z")

</div>

Hi, I’m setting up bloomreach and try executing client-side-renderer example. Have cleared CORS issue, now it says “GET [http://localhost:8080/site/resourceapi](http://localhost:8080/site/resourceapi) 404”. resource api is 404, tried directly in browser url, it is 404.

> Error! Status code 404 while fetching CMS page data for URL: [http://localhost:8080/site/resourceapi](http://localhost:8080/site/resourceapi)

Kindly help.

---

<div class="post-metadata">

**Author:** ![bcanvural](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/bcanvural/32/235_2.png) [@bcanvural](https://community.bloomreach.com/u/bcanvural)\
**Post date:** [April 18, 2019, 11:46am UTC](https://community.bloomreach.com/t/unable-to-run-react-example/988/2 "2019-04-18T11:46:42Z")

</div>

you should add the necessary property on the mount. It is mentioned here: [https://documentation.bloomreach.com/library/concepts/spa-plus/configuration.html](https://documentation.bloomreach.com/library/concepts/spa-plus/configuration.html)

---

<div class="post-metadata">

**Author:** ![SathishKannan](https://avatars.discourse-cdn.com/v4/letter/s/6a8cbe/32.png) [@SathishKannan](https://community.bloomreach.com/u/SathishKannan)\
**Post date:** [April 18, 2019, 12:58pm UTC](https://community.bloomreach.com/t/unable-to-run-react-example/988/3 "2019-04-18T12:58:30Z")

</div>

Thank you @bcanvural, adding `hst:pagemodelapi = resourceapi`  
property resolved this.
