An API to access data and asset context for remote assets / operations monitoring programattically

Provide a documented REST API for PI to OCS connection and data transfer configuration. This would enable scripting against these configurations, allowing users to update their data transfers automatically, and manage them in a customer-specific way.

OCS APIs need to provide better support for viewing data in different time zones / my local timezone. We should be able to encode UTC UTC+13 when making queries to the system.

The ability to expose the stream type property and UOMs for a stream shared through community in the API.

Citizen data scientists, IT professionals and general OCS users need to use REST API methods in 3rd party applications - including Power BI - to access data or explore data using OCS Portal API Console.
Typically objects not "custom created - where you can specify a human readable Id" and a GUID that requires the user to lookup the Id elsewhere or search through a list of objects is used.

As a OCS real-time-visualization-client I require a Streaming API so that I can avoid continuously polling the REST API.

Similar to the WSS Chanels in PI WebAPI

Or something like PI WebAPI Stream Updates could also work

As a developer working on an application that needs to execute a bulk load of MANY separate streams via the OCS REST API, I would like an option to submit a list of streams with start/end index as well as per-stream continuation token, and get raw data back for all the streams. The experience should be as similar as possible as when I'm reading a single stream and the response payload should include the identifier associated with each stream as well as a per-stream continuation token.

The ability share trends as encoded URLs is incredibly useful.

Another area where exploration and collaboration can be done is in the API Console, and there I'd love the ability to craft a query URI and then be able to save that query with a single click and share it directly with a colleague--and I'm not talking about simply sharing the actual REST request URI, I'm more thinking of a link that would open the API Console with that URI already populated, so that my coworkers can start inspecting the same raw data that I'd presented.

As a service provider, I need to incorporate data into our multi-tenant customer portal (custom) SO THAT we can share data and other information with our customers.

Currently, when executing a Data Views data call in the API Console, there is a checkbox for "Return tabular data (form=tableh)", but the form parameter has five possible values. Instead of a checkbox, if the form Parameter were exposed as a drop down of possible values, or even a free-form text box, it would better expose the possible values for this parameter.

I would like to be able to delete a single entry in the favorites rather than deleting the whole list every time.

Being able to save API Console favorite is great, but it would be nice to be able to tag or name them because sometimes the URL gets very long and it is hard to tell which one you want to go to.

Some of the different OCS API resources (streams, assets, data views, etc) use different methods of accessing the information.

For example, in some you may use the ID, others may use the name, others may use ID or name.

This inconsistency makes it more difficult for a developer to leverage the API.

Working with the SDS, it would be nice to be able to specify non equal time interval when looking at monthly summaries for example.

Alternatively, it might be useful to support providing an array of indexes defining the different interval as an alternative to only providing a count between two boundaries.

Lastly, having the flexibility to ask/return only a subset of the summary value (out of the 12 provided) might help with performance and filtering out summary value that have no mathematical sense depending upon the data type and index type being used.

As a data scientist or UI user, I don't know how much data I'm requesting when I ask for a sequence of data. However, I can provide some boundary conditions to help scope the request SO THAT OCS can deliver an appropriate level of detail for my use. This API would support this Visualization UserVoice suggestion: https://feedback.osisoft.com/forums/597811-osisoft-cloud-services/suggestions/34492885-store-pre-computed-averages-to-accelerate-data-scr