canonical: https://jentic.com/apis/endress.com/netilion

# Endress Netilion API

Jentic publishes the only available OpenAPI specification for Netilion API, keeping it validated and agent-ready. Netilion is the Endress+Hauser industrial IoT platform; the API exposes deep coverage of assets, instruments, documents, events, deliveries, and subscriptions for connected process-instrumentation fleets. Plant operators and OEMs use it to register devices, attach calibration documents, record events, and pull asset history. With 799 endpoints, Netilion covers most lifecycle operations for industrial sensors and valves managed in the platform.

## For AI agents

Manage industrial IoT assets, attached documents, events, and subscriptions in the Netilion platform - built for process-instrumentation fleets.

## Scope

Does not handle live process-control loops, real-time SCADA telemetry, or PLC programming - use for managing industrial asset records, attached documents, events, and subscriptions in Netilion only.

## Capabilities

- Register and inspect industrial assets such as sensors, transmitters, and valves
- Attach and retrieve calibration certificates and other asset documents
- Record and query events tied to a specific asset's history
- Manage API subscriptions that gate plan-level entitlements
- Track deliveries that move assets between plants or owners

## Use cases

### Industrial Asset Registration

When a new field instrument is commissioned, an agent registers it in Netilion via POST /assets so it can be tracked across its lifecycle. Subsequent calls attach documents, record events, and link the asset to its parent plant or unit. This replaces hand-keyed asset rosters in spreadsheets and keeps the digital twin accurate from day one.

Example prompt: Create a new asset in Netilion with serial number 'SN-44211' and tag name 'PT-104'

### Calibration Document Retrieval

Maintenance engineers can pull calibration certificates by asset via GET `/assets/{asset_id}/documents.` The agent surfaces the latest certificate so technicians have it on a tablet at the device, satisfying audit and traceability requirements without a trip back to the office.

Example prompt: Fetch all documents attached to asset_id 12345 and return the latest calibration certificate URL

### Asset History and Event Audit

Pull the chronological event history of an asset via GET `/assets/{asset_id}/history/status` to investigate failures, replacements, or status changes. With 799 endpoints, the spec also supports drilling into deliveries, add-ons, and parent groupings around the same asset.

Example prompt: Return the full status history for asset_id 9876 over the last 90 days

### Agent-Driven Plant Operations

An AI agent supporting plant operations searches Jentic for 'list industrial assets', loads the Netilion assets schema, and chains follow-up calls to documents and events. This lets a single agent answer 'what's the calibration status across plant 7?' without any custom Netilion client code.

Example prompt: List all assets in the workspace, fetch each asset's latest event, and return any assets in 'maintenance required' status

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/assets` | List assets |
| GET | `/assets/{id}` | Get an asset by ID |
| GET | `/assets/{asset_id}/documents` | List documents attached to an asset |
| GET | `/assets/{asset_id}/history/status` | Get an asset's status history |
| GET | `/assets/{asset_id}/deliveries` | List deliveries for an asset |
| GET | `/api_subscriptions` | List API subscriptions |
| GET | `/api_keys` | List API keys for the tenant |

## Key resources

- **Assets** — Industrial assets such as sensors and instruments
- **Documents** — Files attached to assets including calibration certificates
- **Events** — Lifecycle and status events for assets
- **API Subscriptions** — Plan-level subscription management
- **Add-ons** — Optional capabilities attached to subscriptions

## Why Jentic

- **Setup:** Wiring the Netilion API by hand means combining basic auth with an API-Key header, working through its 799 operations across assets, documents, events, and subscriptions, and building your own retries against https://api.netilion.endress.com/v1. Through Jentic you install once, import the Netilion API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The Netilion API puts the asset id in the URL path (`/assets/{id}` and `/assets/{asset_id}/...`), so a rule can pin your agent to one industrial asset: it can read that asset's details, documents, status history, and deliveries and nothing else. You choose the operations it may call, so ones touching API keys or subscriptions are not included unless you add them.
- **Credential handling:** Your Netilion credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read an industrial asset record' or 'list documents attached to an asset', and Jentic returns the matching Netilion operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Endurain** — Both surface time-series and asset-style records, but Endurain is for fitness activities while Netilion is industrial IoT.
- **EngageBay CRM REST API** — EngageBay can hold the customer or plant-owner record that Netilion's assets are linked to.
- **Endor Labs AppSec API** — Endor Labs secures the software running plant-floor systems; Netilion manages the physical assets themselves.

## FAQ

### Why is there no official OpenAPI spec for Netilion API?

Endress+Hauser does not publish an OpenAPI specification through public channels. Jentic generates and maintains this spec so that AI agents and developers can call Netilion API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Netilion API use?

Netilion supports both HTTP Basic auth and API key authentication. Through Jentic, both credential types are stored encrypted in the vault and injected at execution time, so the agent never holds the raw secrets in its context.

### Can I retrieve calibration certificates via the Netilion API?

Yes. GET `/assets/{asset_id}/documents` lists every document attached to an asset, including calibration certificates. Filter or sort the result client-side to surface the latest certificate.

### How many assets and endpoints does the Netilion API cover?

The spec documents 799 endpoints, with deep coverage of assets, documents, events, deliveries, subscriptions, and add-ons - enough to manage an entire industrial-instrumentation fleet through code.

### What are the rate limits for the Netilion API?

The spec does not declare rate limits. Endress+Hauser enforces tenant-level throttling in production; back off on HTTP 429 responses and confirm exact limits with your Netilion subscription terms.

### How do I list assets through Jentic?

Run `pip install jentic`, search 'list netilion industrial assets', and Jentic returns GET /assets with its input schema. The agent supplies any filters and executes against base URL https://api.netilion.endress.com/v1.

### Can I limit what my agent is allowed to do with the Netilion API?

Yes. Because you run Jentic One yourself, your own rules decide which Netilion operations and credentials the agent may use. Since the API carries the asset id in the URL path (`/assets/{id}` and `/assets/{asset_id}/...`), you can pin the agent to a single asset so it only reads that asset's details, documents, status history, and deliveries. You also choose the operations it can call, so ones touching API keys or subscriptions stay off unless you add them.