External API suddenly returning error

[horowitzio]

I had a previous topic with a similar situation, but the details are different this time.

I have an External API Global set up with monday.com. It has bee working for months. It stopped working briefly (returning 403 errors), and disabling IPv6 fixed it. IPv6 remains disabled.

Today I noticed the data was missing again. Checking the API Tester, now my API is returning a 400 error. According to monday.com documentation, this is usually malformed query or malformed JSON.

Again, this had all been working for many months. When I replicate the setup I have in Postman, with the same headers and the same GraphQL query, everything works (as it always has).

In Cornerstone/Pro, I am only seeing the error number, not the error description from the API endpoint. I don’t know how to troubleshoot this further since it works in Postman.

[ruenel]

Hey Samuel,

Thanks for writing in!

The given credentials does not seem to work for us.
Please double check it.

Cheers.

[horowitzio]

It should be working now.

[horowitzio]

I also updated the secure note with more specifics on one of the queries, but all of them are currently returning the same error from Cornerstone.

[charlie]

So this was a weird one, but I guess in the case of this API if you send empty variables the API rejects the request. Setting the variables to any sort of object allowed me to get a proper response from the API. On our end we’ll update our GraphQL integration where it won’t send the variables key if you aren’t using the variables and in my testing that got a proper response without needing to do what I do in the screenshot. Let us know if this helps and have a great day.

[horowitzio]

Thank you, adding test variables got all the API pages working again.

[christian]

Glad to hear that, Samuel.