# Problem with mapping after API request

**URL:** <https://forum.litium.com/t/problem-with-mapping-after-api-request/819>\
**Category:** Questions\
**Tags:** litium-7\
**Created:** [April 25, 2019, 7:02am UTC](https://forum.litium.com/t/problem-with-mapping-after-api-request/819 "2019-04-25T07:02:53Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![NilsN](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.litium.com/nilsn/32/302_2.png) [@NilsN](https://forum.litium.com/u/NilsN)\
**Post date:** [April 25, 2019, 1:07pm UTC](https://forum.litium.com/t/problem-with-mapping-after-api-request/819/9 "2019-04-25T13:07:08Z")

</div>

For external API calls you need to include the “litium-request-context” header.

> [@RequestModel null in Api](https://forum.litium.com/t/requestmodel-null-in-api/445/2):
>
> You need to send the ‘litium-request-context’ in the request header so the server can detect the Request context. The value of ‘litium-request-context’ header should be an instance of SiteSettingViewModel

Some more discussion here:  
[https://forum.litium.com/t/moving-clientcontext-to-external-call/](https://forum.litium.com/t/moving-clientcontext-to-external-call/)

---

_[View the full topic](https://forum.litium.com/t/problem-with-mapping-after-api-request/819)._