groov View Public API

Name: groov View Public API API
Brand: groov View Public API
Availability: InStock

✓ Official Vendor SpecIOTDevice ManagementapiKey10 EndpointsREST

For Agents

Read and write data store tag values on Opto 22 groov controllers and pull groov logs over HTTPS using an API key.

Connect the groov View Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the groov View Public API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with groov View Public API API.

Read individual data store tag values from a groov controller

Write values to data store tags on a groov device

List data store devices configured on the controller

Enumerate tags exposed by a connected data store device

GET STARTED

Start building with groov View Public API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use groov View Public API API for, with concrete tasks.

★ Industrial Tag Bridge to Cloud Dashboards

Stream live tag values from a groov EPIC or groov RIO controller into a cloud dashboard or historian. The API exposes per-tag read endpoints so an integration can poll the values it needs without any custom firmware on the controller, using an API key configured in groov Manage.

GET /v1/data-store/devices to list devices, then GET /v1/data-store/read/{id} to fetch the current value of a target tag every 30 seconds

Remote Setpoint Updates from Business Systems

Allow an MES or scheduling system to push setpoints into a groov controller without operator intervention. The write endpoint accepts a tag id and value, so a job-start workflow can set a recipe parameter directly on the device.

POST /v1/data-store/write/{id} with the new setpoint value when an MES job changes recipe

Controller Log Collection for Diagnostics

Pull groov system logs into an external observability stack to investigate connectivity drops or authentication failures. The logging endpoint returns the groovLogs.json payload that operations teams normally read inside groov Manage.

GET /v1/logging/groovLogs.json after an alert fires and forward the response to an incident channel

Agent-Driven Industrial Tag Operations via Jentic

An AI assistant for plant engineers can read and write groov tag values on demand through Jentic without exposing the API key to the model. The agent searches by intent like 'read a groov tag value' and Jentic returns the matching read or write operation with its schema.

Search Jentic for 'read a groov tag value', load the /v1/data-store/read/{id} schema, and execute against the engineer's controller

Key Endpoints

10 endpoints — the groov view public api exposes the data store of an opto 22 groov epic or groov rio industrial controller, letting external systems read and write tag values and device metadata over https.

METHOD

PATH

DESCRIPTION

GET

/v1/data-store/devices

List data store devices

GET

/v1/data-store/devices/{id}/tags

List tags on a device

GET

/v1/data-store/read/{id}

Read a tag value

POST

/v1/data-store/write/{id}

Write a tag value

GET

/v1/logging/groovLogs.json

Retrieve groov system logs

GET

/info

Get server info

GET

/v1/data-store/devices

List data store devices

GET

/v1/data-store/devices/{id}/tags

List tags on a device

GET

/v1/data-store/read/{id}

Read a tag value

POST

/v1/data-store/write/{id}

Write a tag value

GET

/v1/logging/groovLogs.json

Retrieve groov system logs

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The groov API key is stored encrypted in the Jentic vault. Agents receive a scoped session so they can call read and write endpoints without ever seeing the raw API key.

Intent-based discovery

Agents search by intent like 'read a groov tag' or 'write a setpoint to a groov controller' and Jentic returns the matching read or write operation with its parameter schema.

Time to first call

Direct integration: 1-2 days to wire up groov authentication, error handling, and tag id lookups. Through Jentic: under 30 minutes — search, load, execute against your controller.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

PAC Control REST API

Same vendor, but for SNAP-PAC controllers rather than groov EPIC or RIO

Choose PAC Control when the target hardware is a SNAP-PAC-R or -S series controller; groov View targets groov-family controllers.

Alternative

Particle Device Cloud API

General-purpose IoT device cloud for variable read and function call rather than industrial PLC tags

Use Particle when the device fleet is Particle-branded microcontrollers; groov View is the right choice for Opto 22 industrial automation hardware.

Alternative

Blynk IoT API

IoT platform API focused on consumer and prosumer device dashboards

Pick Blynk for consumer-grade connected devices and mobile dashboards; pick groov View for industrial controllers on a plant floor.

FAQs

Specific to using groov View Public API API through Jentic.

What authentication does the groov View Public API use?

The API uses an API key passed as an apiKey credential. The key is created in groov Manage and scoped to the device's data store; through Jentic, the key is held in the encrypted vault and the agent receives only a scoped session, so the raw key never reaches the model context.

Can I write tag values to a groov controller with this API?

Yes. POST /v1/data-store/write/{id} accepts a value for a specific data store tag id, which lets external systems push setpoints or commands into the controller. The companion GET /v1/data-store/read/{id} returns the current value of the same tag.

How many endpoints does the groov View Public API expose?

Ten endpoints across four areas: device and tag enumeration, tag read, tag write, and log retrieval. The surface is intentionally narrow because everything routes through the data store abstraction on the groov controller.

What are the rate limits for the groov View Public API?

Rate limits are not declared in the spec — practical limits are bounded by the groov controller's CPU and the polling interval you configure. Treat the controller as a real-time device and avoid aggressive sub-second polling against multiple tags simultaneously.

How do I read a tag value through Jentic?

Install the Jentic SDK with pip install jentic, then search for 'read a groov tag value'. Jentic returns the GET /v1/data-store/read/{id} operation with its input schema; load it, supply the tag id, and execute. Sign up at https://app.jentic.com/sign-up to get an agent API key.