Endress Netilion API

Name: Netilion API
Brand: Netilion API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementbasic, apiKey799 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Netilion API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Netilion 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 Netilion API.

Attach and retrieve calibration certificates and other asset documents

Record and query events tied to a specific asset's history

GET STARTED

Start building with Netilion API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Netilion API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

799 endpoints — jentic publishes the only available openapi specification for netilion api, keeping it validated and agent-ready.

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

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

Why Jentic?

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

Credential isolation

Netilion supports both Basic auth and API keys; both are stored encrypted in the Jentic vault and supplied to requests at execution time, so the raw credentials never enter the agent's prompt.

Intent-based discovery

Across 799 endpoints, agents search by intent (e.g. 'list industrial assets') and Jentic returns the matching Netilion operation with its input schema, avoiding manual spec spelunking.

Time to first call

Direct Netilion integration: 1-2 weeks to navigate 799 endpoints, dual auth, and pagination. Through Jentic: under 1 hour per intent — search, load, execute.

FAQs

Specific to using Netilion API through Jentic.

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 at https://app.jentic.com/sign-up.

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.