Today we're making a new Fake News category (ID: 868) available in the API. You'll start seeing this category appear in API responses, and you'll be able to filter your queries using it.

Today we are announcing a deprecation period for the ‘mayhem’ categories filter. This affects all endpoints that accept the categories filter:

Customers and friends of NewsWhip look forward to our monthly rankings, showing which publishers are getting the most engagement. It often results in lively debate and a little friendly rivalry between journalists at different publications. This month, we started to use our Stats API to generate the report.

In this release we removed Syndication features from the v1/articles endpoint, as previously advised in this deprecation notice. The matched_rate and matched_sourceId fields will no longer appear in the API response.

In this release, we have made improvements to the Facebook data that we provide in all of our endpoints and also fixed an issue where a low number of results was returned in the v1/articles response when searching using the full text option.

Today we are announcing a deprecation period for the matched_rate and matched_sourceId fields in the v1/articles API response.

Two releases in one day! Double whammy.

This release fixes an issue where filtering for more than one URL in the filters parameter of the v1/articles endpoint would result in a 400 - bad query error.

On behalf of the API team at NewsWhip, it is my pleasure to announce the launch of our Developer Hub.

Traditionally we've grouped our APIs into three plans. The first, optimised for the most common real-time use cases, was the GET API. The second, with historical data going as far back as 2014, was the POST API. Finally, the Syndication API, for newswire services.