canonical: https://jentic.com/apis/swaggerhub.edgezeroapis/lv-monitoring-device-apis

# Edgezero LV Monitoring device APIs

Contains GET only APIs to retrieve interval data. Note : This APIs support "API token based request". The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically returns device details based on the API key, returns event details based on the device_serialid provided within the time stam. Covers 8 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Returns device details based on the API Key
- For any given “as-of” date, this endpoint looks back over the preceding 7-day wi
- Integrate LV Monitoring device APIs into automated workflows
- Query and filter LV Monitoring device APIs records by parameters
- Monitor LV Monitoring device APIs operational status and events

## Use cases

### CRM Operations

Use the LV Monitoring device APIs to perform crm operations programmatically. The API provides 8 endpoints covering core functionality including returns device details based on the API key, returns event details based on the device_serialid provided within the time stam, returns all devices based on the tags provided within the time stamps.

Example prompt: Call GET /devices to returns device details based on the API key

### Automated Devices Management

Automate devices operations by combining multiple LV Monitoring device APIs endpoints. Agents can returns event details based on the device_serialid provided within the time stam and then returns all devices based on the tags provided within the time stamps in a single workflow.

Example prompt: Call GET `/events/interval/{device_serialid}` to returns event details based on the device_serialid provided within the time stam, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call LV Monitoring device APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'returns device details based on the API key', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/devices` | Returns device details based on the API Key |
| GET | `/events/interval/{device_serialid}` | Returns event details based on the device_serialid provided within the time stam |
| GET | `/events/` | Returns all devices based on the tags provided within the time stamps |
| GET | `/powerquality/live/{device_serialid}` | Returns live power quality based on the serialid provided |
| GET | `/powerquality/interval/{device_serialid}` | Returns power quality data based on the provided serialid and the time stamps |
| GET | `/harmonics/interval/{device_serialid}` | Returns harmonics data based on the provided serialid and the time stamps |
| GET | `/pq_performance/interval/{device_serialid}` | For any given “as-of” date, this endpoint looks back over the preceding 7-day wi |
| GET | `/pq_performance_summary/interval/{device_serialid}` | For any given “as-of” date, this endpoint provides the summary of the preceding |

## Key resources

- **Devices** — Operations for devices
- **Events** — Operations for events
- **Harmonics** — Operations for harmonics
- **Powerquality** — Operations for powerquality
- **Pq_Performance** — Operations for pq_performance

## Why Jentic

- **Setup:** Wiring the LV Monitoring device APIs by hand means learning their X-API-KEY header auth, pointing at the v2.edgezeroapi.com Ausgrid host, and hand-coding each device and power-quality call with its retries yourself. Through Jentic you install once, import the LV Monitoring device APIs from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The LV Monitoring device APIs put the device serial id in the URL path (`/powerquality/interval/{device_serialid}`), so a rule can pin your agent to one device: it can read that device's events, power quality, and harmonics and nothing else. You choose the operations it may call, and since every endpoint here is read-only, the agent only retrieves data unless you add more.
- **Credential handling:** Your LV Monitoring device API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list monitoring devices' or 'read a device's power quality interval', and Jentic returns the matching LV Monitoring operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the LV Monitoring device APIs use?

The LV Monitoring device APIs uses an API key passed in the `X-API-KEY` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I returns device details based on the API key with the LV Monitoring device APIs?

Yes. Use the GET /devices endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the LV Monitoring device APIs?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I returns device details based on the API key through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns device details based on the API key'. Jentic returns the matching LV Monitoring device APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the LV Monitoring device APIs have?

The LV Monitoring device APIs exposes 8 endpoints covering devices, events, harmonics operations.

### Can I limit what my agent is allowed to do with the LV Monitoring device APIs?

Yes. Because you run Jentic One yourself, you set the rules that decide which LV Monitoring operations and credentials your agent may use. Since the device serial id sits in the URL path, such as GET `/powerquality/interval/{device_serialid}`, you can pin the agent to a single device so it reads only that device's events, power quality, and harmonics. Every endpoint here is read-only, so with these limits the agent can retrieve interval and live data but cannot change anything.