# Api calls keep getting An invalid response was received from the upstream server

**URL:** <https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989>\
**Category:** Bugs & Issues\
**Created:** [February 14, 2023, 12:02pm UTC](https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989 "2023-02-14T12:02:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![NWE](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nwe/32/4696_2.png) [@NWE](https://community.fibery.io/u/NWE)\
**Post date:** [February 14, 2023, 12:02pm UTC](https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989/1 "2023-02-14T12:02:40Z")

</div>

Hey, I’ve been using fibery API and it has always worked but today, the same api requests I keep getting either

An invalid response was received from the upstream server

or

```auto
{
  "message": "Missing query"
}

```

I haven’t changed my query at all, worked just just earlier today

Edit:

Seems like I get the same when I run it manually through graphql editor

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/37f8dbd32eadd7162c9ef4bef8ed4e0b9d7c4e02.png)

---

<div class="post-metadata">

**Author:** ![Oleg](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oleg/32/1887_2.png) [@Oleg](https://community.fibery.io/u/Oleg)\
**Post date:** [February 14, 2023, 4:48pm UTC](https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989/2 "2023-02-14T16:48:39Z")

</div>

Hi, @NWE

Thanks for letting us know. We just upgraded graphql framework to latest version. Will investigate your case. Could you please try again to execute query? We provided some performance tweaks.

Thanks,  
Oleg

---

<div class="post-metadata">

**Author:** ![NWE](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nwe/32/4696_2.png) [@NWE](https://community.fibery.io/u/NWE)\
**Post date:** [February 14, 2023, 6:09pm UTC](https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989/3 "2023-02-14T18:09:19Z")

</div>

Same thing unfortunately, was done 10 mins ago

```auto
 "data": {
            "errors": [
                {
                    "message": "Missing query"
                }
            ]
        }

```

---

<div class="post-metadata">

**Author:** ![NWE](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nwe/32/4696_2.png) [@NWE](https://community.fibery.io/u/NWE)\
**Post date:** [February 14, 2023, 6:47pm UTC](https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989/4 "2023-02-14T18:47:10Z")

</div>

Did the upgrade change the request form?

I managed to do it from postman

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/35dfb4c982bc77989bad5bf43b2f4d73906f1bfd.png)

Now I guess I need to figure out how to do it from Integromat http module if that is the case

---

<div class="post-metadata">

**Author:** ![NWE](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nwe/32/4696_2.png) [@NWE](https://community.fibery.io/u/NWE)\
**Post date:** [February 14, 2023, 6:51pm UTC](https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989/5 "2023-02-14T18:51:05Z")

</div>

Update:

Apparently the above graphql translates to this http raw

```auto
{"query":"query{findPhones(groupId:{is:177}){id}}","variables":{}}

```

---

<div class="post-metadata">

**Author:** ![NWE](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nwe/32/4696_2.png) [@NWE](https://community.fibery.io/u/NWE)\
**Post date:** [February 15, 2023, 8:07am UTC](https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989/6 "2023-02-15T08:07:50Z")

</div>

@Oleg Can you confirm the request itself has changed for this upgraded graphql version?

Doing it from a ‘http module’

Old way using the query in a query string:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/32b763646a8cbda0aa0252d4bdaea0c0b4423af8.png)

New way using it as a raw request  
 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/49acd0074442a94b1a22486ba6154d6cd64b87cd.png)

If i know this it the new way I could make changes on my side but of its something that will get changed I would prefer to know, thanks in advance

---

<div class="post-metadata">

**Author:** ![Oleg](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oleg/32/1887_2.png) [@Oleg](https://community.fibery.io/u/Oleg)\
**Post date:** [February 15, 2023, 8:42am UTC](https://community.fibery.io/t/api-calls-keep-getting-an-invalid-response-was-received-from-the-upstream-server/3989/7 "2023-02-15T08:42:03Z")

</div>

Hi, @NWE

The way to post graphql query is not changed. We had a lot of tests and all of them kept in the same state as before upgrade. I checked querying in Postman and it works in the same way for me as before upgrade. I use JSON POST.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/118d80bd7b3ef1712250a4f040b2d65daba95d3e.png)