Introduction

the factry historian api gives developers direct programmatic access to data stored in factry historian with it, you can query, retrieve, and interact with time series data, events, the asset tree, in a secure and structured way we provide a openapi (swagger) specification docid\ qe3dszurodfwuvb3ofmmn , making it easy to explore available endpoints, understand request/response formats, and integrate historian data into your own applications, dashboards, or analytics workflows have a look at the python examples docid\ lspqiql9j4kyfsa1nmf4a to interact with the factry historian api using python openapi validation layer in historian v8 2 we introduced a validation layer on top of the api that automatically validates all requests against our openapi specification this ensures all interactions with the api are as described in the spec for this we rewrote large portions of the openapi spec, making it more strict in certain places than before this can cause certain legacy integrations to stop functioning if they depend on the more loose input validation performed before this update if you are encountering problems with the new validation layer, it can be disabled using the environment variable openapi validation enabled setting this to false will disable the api validation layer, allowing the more loose legacy integrations do note that this opens up the historian api to faulty data inputs which may result in unexpected behavior