Hi Dojo,

A while back I attended Kata #18: Creating a scripted connector to learn about scripted connectors.  This was great for me to practice around and see this new feature in action!

One of the items that was mentioned, is that “today” this API can only be leveraged from within the DataMiner system only. And it seems Skyline already listed this features extension to become available later down the line (date to be defined):

Enabling Data API to accept requests from external systems, providing the capability to host your Scripted Connectors in your own environment and, for example, leverage them to push data from the ground to the cloud, from docker containers, from one operational domain to another, etc.

I’m having a use case where I already wanted to push content from an external system into my cloud connected DataMiner system using this DataAPI.

In order to bypass & workaround, I’m combining this DataAPI feature along with the use of custom User Defined APIs (Thank you Kata #2: User-Defined APIs).

Please have a look at the DataAPI-Proxy script (GitHub) that I created. This proxy script can be used out of the box to transfer messages from external systems onto the local DataAPI “scripted connectors”.

I have added an extensive “readme” on the repo  in order to guide you through the steps to setup this proxy on any DataMiner system.

Note:
With every data push this will generate a script-run. Also taking into account that the DataAPI feature is still in soft launch, It’s advised for testing this solely on staging environments for now with a controlled number of requests.

My questions to the community:

• Is there visibility on a ETA when external systems will be allowed to push data into DataAPI?
• Is there any feedback I should consider with my current workaround? (taking into account that I’m managing the number of data pushes to a stable update rate of 1 request / min.

Thank you!