Change Log

# 21 September 2020 - Upcoming changes to Twitter & YouTube data

To stay compliant with the latest Terms of Service for Twitter and YouTube we will be making some changes to the fields we provide through the Meltwater API (previously called the Export API), and Streaming API.

Today we added new Twitter fields to help you update your integration.

Some existing fields will be redacted from the 18th November. Please read the Compliance Changes page for more details.

Twitter Youtube Export Streaming
# 21 September 2020 - Announcing API version 3

We have released a new version of the API which consolidates export and analytics feature into one product. Please read the Migrating to V3 of the API guide to learn more.

Export Analytics
# 27 February 2020 - Removing data_url for INCOMPLETE one-time exports

One-time exports are assigned a status of INCOMPLETE when data for one or more of the searches/tags cannot be exported. In these cases, the data_url will return partial/no results, which may result in inconsistencies. Going forward, the data_url will no longer be provided for INCOMPLETE exports.

# 12 December 2019 - Adding Social Echo for Reddit

We have added the field document_social_echo_reddit to the payload. This Social Echo field shows the number of Reddit shares of an editorial article.

Social Echo field are only enabled when you have the Social Premium Package.

# 26 November 2019 - Searches from Explore now fully available in the Export API

If you have purchased Meltwater’s new Explore product you can now create exports through the Export API for the searches set up in Explore as well.

As Explore allows you to search data across different source types (News, Social), an export from an Explore search may contain results from various sources as well. This differs from exports from searches from our Media Intelligence product, where a single search will always contain results from a single source type only!

Note: In order to create exports for your Explore searches with mixed source types, you need to have purchased the appropriate product packages to retrieve the respective source types through the API.

# 12 November 2019 - Adding new reach fields to editorial documents

  • Field source_reach_desktop: The monthly unique desktop visitors to the source of the document.
  • Field source_reach_mobile: The monthly unique mobile visitors to the source of the document.

The existing field source_reach now contains the sum of the two metrics above.

Please check the Meltwater help center if you want to know more regarding the new reach metrics and how articles are measured.

# 20 September 2019 - Removing country from /companies endpoint

We have removed the country field, in the API response of the /companies endpoint. All customers impacted by this change have been informed via email.

# 11 February 2019 - Simplified setup for exports based on tags

We have introduced couple of changes, which should simplify creating exports based on tags:

  • Updated the Export Console to provide selection of existing tags for given company. This will give you a confidence that export is always created for existing / correct tags
  • Updated API to provide an endpoint (export/v1/tags) to list all tags for the given company
  • Updated API to validate tags existence on export creation request. If you are trying to create an export for non-existing tag, you will receive below error:
  "errors": [
      "type": "TAG",
      "title": "Unknown resource",
      "details": "The tag names you provided ([\"tag\"]) are unknown"

# 9 January 2019 - Added two fields `document_earned_traffic` and `document_hidden`

  • Field document_earned_traffic
    Earned Traffic is defined as anonymous web traffic that first visits an article that is defined in your search, and then visits any page on your domain within 7 days that follows.
    This field is enabled when you have the PR-ROI Package.

  • Field document_hidden
    When viewing search results in, it is possible to ‘Hide’ documents, to prevent them from being displayed as part of your seraches.
    This field will be true if a document has been marked as hidden, false otherwise. With this field it’s possible to determine which documents have been hidden and filter them out accordingly as part of your workflow.

# 8 January 2019 - Support for exports based on tags

Happy New Year!

We’ve introduced the ability to carry out an export of data based one or several tags. This can also be combined with search ids. The exported data will include documents that match your provided search ids or any of the tags. Here’s an example request:

  "onetime_export": {
    "search_ids": [123, 456],
    "tags": ["Big data", "API"],
    "start_date": "2019-01-01T00:00:00Z",
    "end_date": "2019-01-04T23:59:59Z"

Note, the tags must correspond to tags you have already created on See the following article for more information on tags: Using Tags

You can also create the export from the Export Console. You can export up to 5 tags and searches in combination for an export.