Closed patrikhermansson closed 7 years ago
I'm working on making the backend error messages more informative. I should have that done by the end of next week, maybe sooner.
But 9 times out of 10 this error happens because you're missing something the backend code is looking for in the request body. Make sure the following are true:
content
field of the request object is an array of tweet objects, each of which contain their user objects (this is how they usually come from Twitter)user_id
and screen_name
are provided in the meta
objectIf none of that works, let me know. In the mean time, I'll prioritize my work on verifying the requests.
Thanks for the answer! Got it to work, think it was because it was sent as form data... A bit more descriptive error messages would be really great :)
Glad I could help. Yes, the middle layer between the client API and the backend classifier would be generously described as a hack job (I wrote it so I can say that :ok_hand:). Follow @TruthyBotOrNot on Twitter for updates .
This answer documented in the Wiki Troubleshooting & FAQ. Please let me know if you have any suggestions for improvements to that page.
I’m getting a 500 server error when I call your endpoint. The app is in nodejs but I don’t think that’s the main problem, I got some error messages before but now I mostly get this. Do you have any idea what could cause this? It’s difficult to debug as it doesn’t give any data.