# Anomalous API results **URL:** https://meta.discourse.org/t/anomalous-api-results/155581 **Category:** Support **Created:** [June 22, 2020, 3:26pm UTC](https://meta.discourse.org/t/anomalous-api-results/155581 "2020-06-22T15:26:09Z") **Posts on this page:** 1 **Showing post:** 7
### Author: ![Ryan\_NR](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ryan_nr/32/133654_2.png) [@Ryan\_NR](https://meta.discourse.org/u/Ryan_NR) #### Post date: [June 25, 2020, 9:31am UTC](https://meta.discourse.org/t/anomalous-api-results/155581/7 "2020-06-25T09:31:40Z")
Hey @Falco - I managed to get through the proxy but I’m now being hit by `403 BAD CSRF` Errors. I see this thread seems kinda unfinished… > [@Improve BAD CSRF error message when making API calls with content-type application/json](https://meta.discourse.org/t/improve-bad-csrf-error-message-when-making-api-calls-with-content-type-application-json/117136/4): > > Can you share with me your actual ruby code to make this request? I’m unable to reproduce this locally. Here is the Postman json call I’m making and I’m always getting a response back: [image] Also I don’t think you need the extra post["raw"] parameter. Parameters: {"title"=\>"RT @love\_se4: One of those hidden gems in the local community, you just have to try. Over 170 different gins. Proper mixologists who know h…", "raw"=\>"https://twitter.com/se23\_tweets/status/1127663613412630529"… Do you have any thoughts on how to beat these errors? --- _[View the full topic](https://meta.discourse.org/t/anomalous-api-results/155581)._