Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Historian

Supported versions

  • Last UpdatedMar 19, 2025
  • 2 minute read

Insight supports versions 1 and 2 of the Historian Data REST API.

Version 2

This is the current and recommended version of the Historian Data REST API.

Version 2 of this REST APis based on version 1 and includes further enhancements. Version 2 includes these differences from version 1:

  • The TagFilter parameter is supported as a part of a GET or POST query used with ProcessValues, AnalogSummary, and StateSummary resources.

  • The datetimeoffset parameter is not supported as part of the DateTime syntax.

  • While Raw and ProcessValue entities use DateTime, summary entities use StartDateTime and EndDateTime.

  • For most version 2 queries, single quotes are not used for DateTime. For example:

    https://online.wonderware.[DOMAINSUFFIX]/apis/Historian/v2/ProcessValues
    ?$filter=DateTime+gt+2017-07-13T00:00:00

    However, when querying events, single quotes are required for DateTime. For example:

    https://online.wonderware.[DOMAINSUFFIX]/apis/Historian/v2/Events
    ?$filter=EventTime+gt+'2017-07-13T00:00:00'

    By contrast, version 1 queries do use single quotes for DateTime. For example:

    https://online.wonderware.[DOMAINSUFFIX]/apis/Historian/v1/ProcessValues
    ?$filter=DateTime+gt+datetimeoffset'2017-07-13T00:00:00'

  • TagProperty and Events entity types are now open type. That is, dynamic properties can be added to the response at runtime. This can be verified using $metadata endpoint URL:

    https://online.wonderware.[DOMAINSUFFIX]/s/<solution_id>/apis/historian/v2/$metadata

    where there will be additional attribute, OpenType="true", under <EntityType> section.

  • The Tags resource returns all the properties (fixed and extended) for a tag. A tag's extended properties will be added to the response only if they exist. (The extended property name will not be listed for tags that do not have a given extended property.)

  • The combined Summary resource is not supported in version 2. Use the individual AnalogSummary and StateSummary resources instead to retrieve the summary of a tag.

  • Insight returns a list of resources and endpoints in JSON format instead of the previously used XML when you specify the default endpoint URL for your solution (where <solution_id> is the identifier for your Insight solution:

    https://online.wonderware.[DOMAINSUFFIX]/s/<solution_id>/apis/historian/v2

  • Version 2 adds support for the OData contains function for applicable resources and properties.

Version 1

This is the original version of Historian Data REST API based on the OData v4 specification.

  • Version 1 uses the DateTime format used in this example:

    https://online.wonderware.[DOMAINSUFFIX]/s/ik97r5/apis/Historian/v1
    /AnalogSummary?$filter=FQN+eq+'Baytown.tank_level'
    +and+StartDateTime+ge+datetimeoffset'2016-05-14T00:00:00.000-07:00'
    +and+EndDateTime+le+datetimeoffset'2016-05-16T00:00:00.000-07:00'

In This Topic
TitleResults for “How to create a CRG?”Also Available in