Ijenko IoE2 IoT API

Name: IoE2 IoT API
Brand: IoE2 IoT API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice ManagementapiKey67 EndpointsREST

For Agents

Manage IoT accounts, places, users, devices, gateways, and sensor data for smart-home and energy management applications.

Install Jentic One Beta

Connect the IoE2 IoT API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IoE2 IoT 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fijenko.net%2Fijenko" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fijenko.net%2Fijenko" | 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 IoE2 IoT API.

List, create, and revoke account-level access tokens via /account/tokens

Manage places (homes, sites) under an account via /account/places

Create, update, and delete users associated with the account

GET STARTED

Start building with IoE2 IoT API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use IoE2 IoT API for, with concrete tasks.

★ Smart Energy Management Portal

Power a utility-branded portal that lets households see real-time energy consumption from gateway-connected meters and sensors. The /account/places endpoints register each home, /account/users manages the household members with portal access, and the device and sensor endpoints pull telemetry for charts and bill-saving recommendations.

List the user's places via GET /account/places, then read the latest electricity sensor reading from each place's primary gateway.

Multi-Tenant IoT Account Management

Manage multi-tenant IoT deployments where each customer has their own account, places, and users. Operations on /account/users and /account/tokens let an admin onboard and offboard accounts, rotate access tokens for security, and propagate metadata changes across the linked places without touching the underlying device fleet.

Rotate the access token for a customer account by listing tokens, deleting the current one, and triggering creation of a new token.

Home Automation Backend

Build a home automation backend that ties places, users, and connected devices together. The API provides the canonical model - places contain gateways, gateways contain sensors and actuators - so an agent or app can render a coherent room-by-room view and dispatch commands or read telemetry.

Walk the place-gateway-sensor hierarchy for a household and produce a dashboard summary.

AI Agent Energy Coach

An AI agent acts as an energy coach: it pulls sensor history for a household via Ijenko, identifies high-usage periods, and recommends behaviour changes. Through Jentic, the agent finds the right Ijenko endpoints from a single intent search, with the access token kept in the vault.

Use Jentic to call GET /account/places, retrieve sensor data for the user's home, and produce a 3-tip energy-saving summary.

Key Endpoints

67 endpoints — the ijenko ioe2 iot api powers end-user iot applications across smart energy, home automation, and connected devices.

METHOD

PATH

DESCRIPTION

GET

/account/places

List places under the account

POST

/account/places

Create a new place

GET

/account/users

List users under the account

POST

/account/users

Create a new user

GET

/account/tokens

List active access tokens

DELETE

/account/tokens/{tokenId}

Revoke an access token

POST

/account/change-password

Change the account password

PATCH

/account/users/{userId}/metadata

Modify user metadata

GET

/account/places

List places under the account

POST

/account/places

Create a new place

GET

/account/users

List users under the account

POST

/account/users

Create a new user

GET

/account/tokens

List active access tokens

DELETE

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the IoE2 IoT API by hand means passing its access token in either an Access-Token header or a query parameter and covering the account, place, user, and sensor endpoints yourself. Through Jentic you install once, import the IoE2 IoT API from the API Directory, store the token once, and your agent calls it.

Permission scoping

IoE2 puts resource ids in the URL path (/account/users/{userId}/metadata, /account/tokens/{tokenId}), so a rule can pin your agent to one user or token. You choose the operations it may call, so destructive ones like deleting a token or changing a password are not included unless you add them.

Credential isolation

Your IoE2 access token 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.

Intent-based discovery

Agents search Jentic by intent such as 'list IoT places' or 'read sensor data', and Jentic returns the matching IoE2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using IoE2 IoT API through Jentic.

What authentication does the Ijenko IoE2 IoT API use?

Ijenko uses an API key passed in the Access-Token header or as a query parameter. Through Jentic, the token is held in the vault and injected at execution time, so the agent never sees the raw secret.

Can I manage multiple homes or sites under one account?

Yes. GET /account/places lists every place under the account and POST /account/places creates a new one. Each place is the container for connected gateways, sensors, and devices.

How do I rotate access tokens for an Ijenko account?

List active tokens with GET /account/tokens, revoke an old one with DELETE /account/tokens/{tokenId}, and request a new token through the account credential flow. Rotate periodically to reduce blast radius if a token leaks.

What are the rate limits for the Ijenko API?

Rate limits are not declared in the OpenAPI spec; Ijenko enforces plan-tier throttles per account. Handle 429 with exponential backoff and contact support for production quotas.

Can I store custom metadata on users or places?

Yes. PATCH /account/users/{userId}/metadata and the equivalent place-metadata endpoints accept structured key-value pairs that the application can use to track tags, segments, or external IDs.

How do I pull sensor data through Jentic?

Run pip install jentic, search 'read sensor data from an iot device', load the relevant Ijenko sensor endpoint, and execute with the place and gateway IDs.

Can I limit what my agent is allowed to do with the Ijenko IoE2 IoT API?

Yes. Because you run Jentic One yourself, your own rules decide which Ijenko operations and credentials the agent may use. Ijenko puts resource ids in the URL path, such as /account/users/{userId}/metadata and /account/tokens/{tokenId}, so a rule can pin the agent to a single user or token. You choose the operations it may call, so read-only work like listing places with GET /account/places or reading sensor data is allowed while destructive calls such as DELETE /account/tokens/{tokenId} or POST /account/change-password stay off unless you add them.

Ijenko IoE2 IoT API

Connect the IoE2 IoT API to your agent

Capabilities

Start building with IoE2 IoT API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs