# Variation in API Response Field Name: status\_code vs statusCode

**URL:** <https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388>\
**Category:** Support\
**Created:** [April 15, 2025, 8:10am UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388 "2025-04-15T08:10:06Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dakshayini\_dev](https://avatars.discourse-cdn.com/v4/letter/d/ebca7d/32.png) [@Dakshayini\_dev](https://community.feathery.io/u/Dakshayini_dev)\
**Post date:** [April 15, 2025, 8:10am UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/1 "2025-04-15T08:10:06Z")

</div>

In the API response triggered from Feathery, the status field randomly switches between status\_code and statusCode. What could be causing this?

---

<div class="post-metadata">

**Author:** ![Kenny](https://avatars.discourse-cdn.com/v4/letter/k/90db22/32.png) [@Kenny](https://community.feathery.io/u/Kenny)\
**Post date:** [April 15, 2025, 8:29am UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/2 "2025-04-15T08:29:08Z")

</div>

Hi @Dakshayini_dev , What api are you using? Are there any scenarios that it populates statusCode/status\_code? or it is pure random?

---

<div class="post-metadata">

**Author:** ![Dakshayini\_dev](https://avatars.discourse-cdn.com/v4/letter/d/ebca7d/32.png) [@Dakshayini\_dev](https://community.feathery.io/u/Dakshayini_dev)\
**Post date:** [April 15, 2025, 2:39pm UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/3 "2025-04-15T14:39:42Z")

</div>

I’m testing the form integration with a GET API that retrieves some object details. The two scenarios I’m validating are:

- Rendering via embedded code inside a JavaScript function, which is triggered by a click event — gives status\_code in API response.

- Rendering the form by embedding the script directly in a simple HTML page — gives statusCode in API response.

---

<div class="post-metadata">

**Author:** ![Kenny](https://avatars.discourse-cdn.com/v4/letter/k/90db22/32.png) [@Kenny](https://community.feathery.io/u/Kenny)\
**Post date:** [April 15, 2025, 2:46pm UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/4 "2025-04-15T14:46:00Z")

</div>

@Dakshayini_dev , If this is a feathery API, can I know which one exactly are you using? I would like to replicate what you are experiencing for us to be in the same picture

---

<div class="post-metadata">

**Author:** ![Dakshayini\_dev](https://avatars.discourse-cdn.com/v4/letter/d/ebca7d/32.png) [@Dakshayini\_dev](https://community.feathery.io/u/Dakshayini_dev)\
**Post date:** [April 16, 2025, 7:34am UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/5 "2025-04-16T07:34:54Z")

</div>

Hey @Kenny, just a clarification — it’s not a Feathery API, it’s an API from our own application. We’re just using **feathery.http.get(url)** to invoke it

---

<div class="post-metadata">

**Author:** ![Kenny](https://avatars.discourse-cdn.com/v4/letter/k/90db22/32.png) [@Kenny](https://community.feathery.io/u/Kenny)\
**Post date:** [April 16, 2025, 7:59am UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/6 "2025-04-16T07:59:14Z")

</div>

Got it. I’ll try to replicate what you experienced and coordinate it with our engineers. Will keep you posted

---

<div class="post-metadata">

**Author:** ![Dakshayini\_dev](https://avatars.discourse-cdn.com/v4/letter/d/ebca7d/32.png) [@Dakshayini\_dev](https://community.feathery.io/u/Dakshayini_dev)\
**Post date:** [April 24, 2025, 3:45pm UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/7 "2025-04-24T15:45:52Z")

</div>

@Kenny Just checking — is there any chance this behavior depends on the specific version of SDK we’re using?

---

<div class="post-metadata">

**Author:** ![Kenny](https://avatars.discourse-cdn.com/v4/letter/k/90db22/32.png) [@Kenny](https://community.feathery.io/u/Kenny)\
**Post date:** [April 25, 2025, 1:55am UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/8 "2025-04-25T01:55:09Z")

</div>

@Dakshayini_dev , We are not able to replicate the scenario you experienced. Can you try getting the latest version of our SDK and see if it’ll become consistent?

---

<div class="post-metadata">

**Author:** ![Dakshayini\_dev](https://avatars.discourse-cdn.com/v4/letter/d/ebca7d/32.png) [@Dakshayini\_dev](https://community.feathery.io/u/Dakshayini_dev)\
**Post date:** [April 30, 2025, 11:19am UTC](https://community.feathery.io/t/variation-in-api-response-field-name-status-code-vs-statuscode/1388/9 "2025-04-30T11:19:32Z")

</div>

We identified the issue — the `status_code` attribute behaves differently between the React SDK and the JavaScript SDK.
