Configure Refinitiv Intelligent Tagging Open Calais as your content tagging provider

Current version: 9.3

Refinitiv Intelligent Tagging analyzes the semantic content of input content using a combination of statistical, machine-learning, and custom pattern-based methods. The algorithms developed by the Text Metadata Services (TMS) group at Thomson Reuters output highly accurate and detailed metadata. For more detailed information, see the official Refinitiv Intelligent Tagging documentation.

The free Refinitiv Intelligent Tagging Open Calais tagging provider lets you use Open Calais to tag your content to increase its value, accessibility, and interoperability. When you establish an Open Calais account, your Sitecore implementation with Sitecore CortexTM Content Tagging can send content to Open Calais. When the content is returned from Open Calais, your Sitecore implementation can extract four different types of tags, which are categorized in Open Calais as Social Tags, Industries, Topics and Entities.

To configure Open Calais as your content tagging discovery provider:

  1. Register a PermID (Thomson Reuters Permanent Identifier) account at


    After you activate your account, you receive an email with your token for API access.

  2. Ensure that the App_Config/Sitecore/ContentTagging/Sitecore.ContentTagging.OpenCalais.config file is enabled.

  3. Create a patch for settings from the App_Config/Sitecore/ContentTagging/Sitecore.ContentTagging.OpenCalais.config file that: 

    • Ensures that the Sitecore.ContentTagging.OpenCalais.CalaisEndpoint setting points to an actual endpoint (this usually does not change over time).

    • Fills in the Sitecore.ContentTagging.OpenCalais.CalaisAccessToken setting with the API access token from Thomas Reuters. 

    • Fills in the Sitecore.ContentTagging.OpenCalais.CalaisLanguage setting with a content language. Currently English, Chinese, French, German, Japanese and Spanish are supported. For more information, see here.

Do you have some feedback for us?

If you have suggestions for improving this article,