External API suddenly returning 403 - other clients are just fine

We use Monday.com to store some data we’d like to show on our website. For a long time this has worked fine using the External API feature. It was working just fine on 3/31, based on an internet archive listing of our page. I have been out of office a lot in April, and I see today that that any pages that reference the API are showing blank. Using the API Tester I am getting a 403 error. The actual error coming from Monday.com seems not to be showing. I’m at a loss on how to troubleshoot. The complexity of the API query should not matter if the issue is an authentication one. I just tried the same API key I’m using through Cornerstone on the command line through curl, with the same query, and I’m getting results in the command line. I hadn’t updated Cornerstone in that time, so I’m not sure why this would have broken. Monday.com says the problem is not on their end. I am at a loss on how to troubleshoot further.

Hello Samuel,

Thanks for writing in! The API Call returns an Error 403 which could mean that the user has no access. Please verify if the user has access to the call. Kindly check out the Erro Handling here:

Hope this helps.

As I said, I can use that same API key from the command line (curl) or Postman and run the same query and return the result. Everything was working fine one month ago, and I don’t know of any changes that would have been made in Cornerstone. Is there anyway to debug with more detail, like see the call that is actually being made to the external API?

Thank you for the update. According to the API documentation, there are two kinds of token, app and personal token. Which type did you generate? Have you tried regenerating another token with complete or full set of permissions?

https://developer.monday.com/api-reference/docs/authentication

We did test the key on the API playground and it worked correctly, but regenerating another token might help.

It’s a personal token. I would like to avoid regenerating the token since it’s working in other places. Since I can run that same query in Postman, with the same token I pasted into Cornerstone, it doesn’t seem like the problem is with the token.

We cloned your monday.com API setup in our installation and it worked as expected, so this is probably an issue with a third-party plugin or a recent change in your server. Have you tried deactivating the plugins temporarily?

So… late last week I disabled IPv6 on my server and all works as expected. Monday.com claims their API should work over either protocol. Is there anything on the client side that should care?

Hello @horowitzio,

Thank you for the update.

If you can provide the S/FTP details, we’ll try to debug the issue further. Please include the information in the secure note field.

Best regards,
Themeco

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