- 8 Feb 2021 - Support for Facebook and Instagram in exports and analytics
- 1 Feb 2021 - Analytics - Expanding top languages and top country codes
- 4 Dec 2020 - Exports - Additional fields for export results
- 13 Nov 2020 - Analytics API - Multi-company support and Author Count Analysis
- 2 Nov 2020 - New analytics endpoints - top keyphrases, top locations, top entities
- 21 Sep 2020 - Upcoming changes to Twitter & YouTube data
- 7 Sep 2020 - Announcing API version 3
- 27 Feb 2020 - Removing data_url for INCOMPLETE one-time exports
- 12 Dec 2019 - Adding Social Echo for Reddit
- 26 Nov 2019 - Searches from Explore now fully available in the Export API
- 12 Nov 2019 - Adding new reach fields to editorial documents
- 20 Sep 2019 - Removing country from /companies endpoint
- 11 Feb 2019 - Simplified setup for exports based on tags
- 9 Jan 2019 - Added two fields `document_earned_traffic` and `document_hidden`
- 8 Jan 2019 - Support for exports based on tags
# 8 February 2021 - Support for Facebook and Instagram in exports and analytics
Today we released changes that add Facebook and Instagram as sources you can use for exports and analytics.
To use these sources you will need to have access to the Premium Social Package. Please contact your account manager if you'd like to add this product to your package.
For exports, if your saved search includes Facebook or Instagram data this will be included in your export. See the formats and fields page for details of available fields.
For analytics (if you have access to this feature), you can now use these sources as the 'source' parameter for many of the analytics endpoints. Please see the endpoint documentation for full details.
# 1 February 2021 - Analytics - Expanding top languages and top country codes
Today we’ve expanded the number of top languages and top country codes returned in the analytics summary api.
We now return a maximum of 50 languages and country codes.
# 4 December 2020 - Exports - Additional fields for export results
Today we’ve added some additional fields to export results:
- Engagement, the total engagement a tweet has seen, has been added to the CSV format (as “Engagement”) and JSON format (as “document_engagement”)
- City & State, have been added to the CSV format (these were already present in JSON format)
- The “Earned Traffic” field which was already present in CSV format has been added to the JSON format as “document_earned_traffic”.
The Exports Formats and Fields page has been updated with these changes.
# 13 November 2020 - Analytics API - Multi-company support and Author Count Analysis
Today we’ve released two new features to the analytics API.
All existing analytics endpoints now support a
company_id parameter, the same way export and search management endpoints do.
If you have multiple companies set up for your Meltwater account, this parameter allows you to specify a search belonging to one of your other companies.
We’ve also added an extra field to the output of the Summary endpoint called
unique_authors, this is a count of the number of unique authors in the window.
If you’re analysing
news it will always return 0, but will work on all other types.
As usual you can see these changes reflected in the Endpoints Documentation.
# 2 November 2020 - New analytics endpoints - top keyphrases, top locations, top entities
Over the last couple of weeks we’ve been working on adding new analytics features to the API.
We’ve added the following new analytics endpoints:
top_keyphrases: provides the top words and keyphrases found in documents that match your search.
top_entities: provides the top entities found in documents that match your search.
top_locations: provides the top locations (countries, states, cities) of authors for documents in your search.
Please see the Endpoints Documentation for more details.
# 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.
# 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
# 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
source_reach_desktop: The monthly unique desktop visitors to the source of the document.
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.
# 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:
# 9 January 2019 - Added two fields `document_earned_traffic` and `document_hidden`
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.
When viewing search results in app.meltwater.com, it is possible to ‘Hide’ documents, to prevent them from being displayed as part of your seraches.
This field will be
trueif a document has been marked as hidden,
falseotherwise. 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:
Note, the tags must correspond to tags you have already created on app.meltwater.com. 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.