# API Issue with the Response Structure

**URL:** https://community.triggre.com/t/api-issue-with-the-response-structure/329
**Category:** Support
**Created:** [May 15, 2023, 3:55pm UTC](https://community.triggre.com/t/api-issue-with-the-response-structure/329 "2023-05-15T15:55:16Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![sven.brossi](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.triggre.com/sven.brossi/32/111_2.png) [@sven.brossi](https://community.triggre.com/u/sven.brossi)
#### Post date: [May 15, 2023, 3:55pm UTC](https://community.triggre.com/t/api-issue-with-the-response-structure/329/1 "2023-05-15T15:55:16Z")

</div>

Hi,

I am trying to use the ChatGPT API and one of the use cases is, that I want to get the list of the currently available ChatGPT models. I defined the API Get request with the response data structure that looks like the following:

1. According to the API description  

2. The structure I defined in the flow part …  

3. What I got after I closed the flow part and reopened it …  

The structure seems to be mixed up. There appears to be an error.

I now try instead of defining permissions as a list to define the “permission” parameter as a text maybe that works.

 ![Bildschirmfoto 2023-05-15 um 17.40.11](https://canada1.discourse-cdn.com/flex035/uploads/triggre/original/1X/dac5578c6624696d9a3ea01787c13730b8db53ce.png)

**I just have the confirmation that this worked although of course, I do not get the permission back!**

Cheers,  
Sven

---

<div class="post-metadata">

### Author: ![Jesse](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.triggre.com/jesse/32/88_2.png) [@Jesse](https://community.triggre.com/u/Jesse)
#### Post date: [May 15, 2023, 4:46pm UTC](https://community.triggre.com/t/api-issue-with-the-response-structure/329/2 "2023-05-15T16:46:51Z")

</div>

Hi @sven.brossi,

Thanks for bringing this to our attention. I will ask the team to look into this because it indeed seems like a defect.

Though in general I think that the structure is still correct, it’s just that the order of the items has changed. This shouldn’t be a problem for the functionality, though I think it should not change from how you defined it.

Please see if it works with the original version, I think you’ll find that will actually work.

@Alex I have created a defect for this.

---

<div class="post-metadata">

### Author: ![sven.brossi](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.triggre.com/sven.brossi/32/111_2.png) [@sven.brossi](https://community.triggre.com/u/sven.brossi)
#### Post date: [May 15, 2023, 5:13pm UTC](https://community.triggre.com/t/api-issue-with-the-response-structure/329/3 "2023-05-15T17:13:33Z")

</div>

Hi @Jesse,

Thank you, I will try it and in case it will not work let you know.

Cheers,  
Sven

---

<div class="post-metadata">

### Author: ![Jesse](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.triggre.com/jesse/32/88_2.png) [@Jesse](https://community.triggre.com/u/Jesse)
#### Post date: [July 12, 2024, 11:25am UTC](https://community.triggre.com/t/api-issue-with-the-response-structure/329/4 "2024-07-12T11:25:27Z")

</div>

Hi @sven.brossi,

A quick update, because it isn’t in the [2024.2 release notes](https://community.triggre.com/t/release-notes-2024-2/746), that this issue was fixed in the 2024.2 release.

It should now keep the order that you typed. Keep in mind that technically there shouldn’t be a difference, the order shouldn’t matter as per the definition of JSON. However, for us mere humans, it can be disorienting when the order changes, of course 🙂

---

<div class="post-metadata">

### Author: ![system](https://canada1.discourse-cdn.com/flex035/uploads/triggre/original/1X/367281c6ef0a1cef3dd636979e56e8a6918e707f.png) [@system](https://community.triggre.com/u/system)
#### Post date: [July 15, 2024, 3:25pm UTC](https://community.triggre.com/t/api-issue-with-the-response-structure/329/5 "2024-07-15T15:25:44Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
