# Case of http headers has changed.

**URL:** <https://community.hubspot.com/t/case-of-http-headers-has-changed/112091>\
**Category:** APIs & Integrations\
**Tags:** professional\
**Created:** [July 16, 2024, 3:53pm UTC](https://community.hubspot.com/t/case-of-http-headers-has-changed/112091 "2024-07-16T15:53:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![MTomaschek](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mtomaschek/32/82797_2.png) [@MTomaschek](https://community.hubspot.com/u/MTomaschek)\
**Post date:** [July 16, 2024, 3:53pm UTC](https://community.hubspot.com/t/case-of-http-headers-has-changed/112091/1 "2024-07-16T15:53:21Z")

</div>

Hi,  
the HubSpot API started returning headers in lowercase a few days ago. Is this an intended change or an accident? I can’t find any post or article about it.  
Examle:  
X-HubSpot-RateLimit-Daily chnaged to x-hubspot-ratelimit-daily  
We can adapt to the change, we just want to be sure that this is the final form and it will not be reverted in a few days…

---

<div class="post-metadata">

**Author:** ![HMir](https://avatars.discourse-cdn.com/v4/letter/h/dec6dc/32.png) [@HMir](https://community.hubspot.com/u/HMir)\
**Post date:** [July 17, 2024, 9:45am UTC](https://community.hubspot.com/t/case-of-http-headers-has-changed/112091/2 "2024-07-17T09:45:49Z")

</div>

> * * *
> 
> @MTomaschek wrote:
> 
> Hi,  
> the HubSpot API started returning headers in lowercase a few days ago. Is this an intended change or an accident? I can’t find any post or article about it.  
> Examle:  
> X-HubSpot-RateLimit-Daily chnaged to x-hubspot-ratelimit-daily  
> We can adapt to the change, we just want to be sure that this is the final form and it will not be reverted in a few days…
> 
> * * *

To handle the change in HTTP header case from the HubSpot API, you can adapt your code to be case-insensitive when reading headers. Most programming languages and libraries provide a way to access headers without considering their case. For example, in Python, you can use a case-insensitive dictionary, and in JavaScript, headers are typically accessed in a case-insensitive manner by default. By implementing a case-insensitive approach to handling headers, you can ensure that your code remains robust and functional regardless of future changes in header case formatting by the API.

---

<div class="post-metadata">

**Author:** ![MTomaschek](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mtomaschek/32/82797_2.png) [@MTomaschek](https://community.hubspot.com/u/MTomaschek)\
**Post date:** [July 17, 2024, 10:37am UTC](https://community.hubspot.com/t/case-of-http-headers-has-changed/112091/3 "2024-07-17T10:37:13Z")

</div>

I am well aware that I can handle it in case insensitive manner, however it’s not possible to do so natively in the tool I am using (I would have to copy the map while lowercasing the entries or try both options).  
All I want is to someone from HubSpot to confirm whether this is a planned change or a bug.