Why did I get a 400 'nonWorkingUrl' from passing in a valid URL?

So you passed in a URL (that loads fine in your browser) as the 'contentUri' to your Rosette API call -- and got a 400. What happened is that our underlying components in the Rosette API use a custom URL text extractor, and sometimes sophisticated sites block our extractor, thinking it's a bot. We're working on catching these cases, and upcoming releases will have improved URL downloading. For now, the workaround is to take the text yourself from the webpage and pass it as text in the 'content' parameter.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.

Powered by Zendesk