GET STARTED
TOOLS
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
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.
ThingsBoard open-source IoT platform REST API documentation. The API exposes 496 endpoints secured with apiKey, loginPassword authentication.
PI Web API exposes the OSIsoft (now AVEVA) PI System over REST, giving programmatic access to the historian, asset framework, analyses, event frames, batch records, and notifications stored across an industrial deployment. With 413 endpoints, it covers reading and writing time-series tags, navigating asset hierarchies, running search across element templates, and configuring security on every PI object. Operators in manufacturing, energy, and utilities use PI Web API to push real-time sensor data into analytics, MES, and digital twin pipelines.
The MIMIC REST API is the programmatic control surface for Gambit Communications' MIMIC simulator, the industry-standard tool for simulating thousands of SNMP, IPMI, NetFlow, sFlow, IoT, and Telnet/SSH devices for network management testing. The 356 endpoints under /mimic let test engineers create simulated agents, configure protocol behaviour, control logging and statistics, manage simulator clients, and orchestrate large-scale lab scenarios from CI pipelines. Authentication uses HTTP basic credentials and the simulator runs locally so the base URL points at 127.0.0.1. The API is targeted at NMS vendors, network operators, and IoT platform builders who need to validate management software against device populations far larger than physical lab inventory allows.
AGCO Aftermarket Tools Service (ATS) is the dealer-facing API for AGCO's agricultural equipment service ecosystem - tractors, engines, ECUs, and aftermarket diagnostic tools across the Massey Ferguson, Fendt, Valtra, and Challenger brands. The 163-path surface covers engine and ECU records by serial number, license activations and authorization codes for diagnostic tooling, dealer client and user administration, software releases and update groups, content submissions and translation sets, and a reporting layer for service operations.
ClearBlade is an industrial IoT platform, and its REST API exposes the platform's full operational surface across systems, devices, collections, code services, message-passing, and developer administration. With over 220 endpoints, the API covers everything from provisioning a new system and registering devices to running data queries, sending MQTT messages, and rotating device keys. Operations are grouped under admin, codes, data, devices, edges, and message-history namespaces, reflecting the platform's multi-tenant edge-and-cloud architecture. It is designed for industrial operators, OEMs, and IoT solution builders who need full programmatic control over a fleet.
Jentic publishes the only available OpenAPI specification for EMnify Enterprise API, keeping it validated and agent-ready. The Enterprise API is EMnify's full administrative surface for IoT connectivity - endpoint and SIM lifecycle, MFA-protected user management, organization and workspace configuration, tariff and service profiles, integrations, and event streams. With 181 endpoints across 19 functional areas, it covers everything from a single SIM update to full multi-tenant fleet operations. Use it when a deployment needs deep platform control rather than the minimal core feature set.
The Hue CLIP API v2 is the local REST interface exposed by every Philips Hue Bridge for controlling and observing the connected smart-home devices. It covers lights, scenes, rooms, zones, motion and contact sensors, smart buttons, entertainment configurations, geofencing, behavior scripts, and bridge-level features such as software updates and Matter and HomeKit pairing. Authentication is via the hue-application-key header issued by the bridge, and all calls are made directly to the bridge IP rather than to a cloud endpoint, so the API is local-network-only.
Jentic publishes the only available OpenAPI specification for Kindoo.Tech, keeping it validated and agent-ready. Kindoo is an access-control and smart-property platform whose API exposes sites (called environments), entry points, access rules, users, agents, licenses, and the session lifecycle that authorizes every request. The 129-endpoint surface covers creating sites, configuring access rules, customising invitation emails per language, retrieving entry-point logs, and managing the SessionTokenID issued by ApiLogin. Use it to wire access control into property management or guest workflow systems.
Jentic publishes the only available OpenAPI specification for Golioth API, keeping it validated and agent-ready. Provision, monitor, and control MCU-based IoT devices through a cloud platform that provides LightDB state storage, LightDB Stream for time-series telemetry, OTA firmware updates via releases and artifacts, device-level RPC calls, and data routing through configurable integrations. The API spans 106 endpoints organized around projects, devices, credentials, blueprints, releases, settings, and cloud-to-device data operations.
Jentic publishes the only available OpenAPI specification for Alexa For Business, keeping it validated and agent-ready. Alexa for Business gives organisations programmatic control over Alexa devices deployed in conference rooms, hotels, and shared workspaces. The API exposes 93 operations covering rooms, profiles, devices, contacts, address books, skills, skill groups, gateways, and network profiles, plus user enrolment and meeting room management. Note that AWS deprecated the Alexa for Business service in 2023; this catalogue entry remains for legacy fleet operations and migration tooling.
Jentic publishes the only available OpenAPI specification for AWS Greengrass, keeping it validated and agent-ready. AWS IoT Greengrass extends AWS onto edge devices so they can run Lambda functions, machine learning inference, and local messaging while staying connected to the cloud for management and analytics. The Greengrass v1 control-plane API manages groups, cores, devices, function definitions, subscription tables, resource definitions, and deployments across 92 operations. It is the orchestration layer for fleet-wide configuration of Greengrass cores running at the edge.
Jentic publishes the only available OpenAPI specification for Balena Cloud API, keeping it validated and agent-ready. Deploy and manage containerized applications across fleets of Linux single-board computers using an OData-based REST API with 82 endpoints. The API covers fleet (application) management, device provisioning and state control, release tracking, environment variable configuration, tagging, API key management, and organization administration - all queryable with $filter, $select, $expand, $orderby, $top, and $skip operators.
Jentic publishes the only available OpenAPI specification for Blues Notehub API, keeping it validated and agent-ready. This blues.io listing covers the broader 81-endpoint Notehub surface, including projects, products, fleets, devices, notes, events, routes, monitors, environment variables, firmware updates, billing accounts, and usage data. Notehub is the cloud counterpart to the Blues Notecard cellular module, and the API supports remote firmware delivery, per-device enable and disable, and full lifecycle management for cellular IoT deployments. Authentication uses Bearer tokens obtained from /oauth2/token.
The Brain Web API is the REST surface of Intellifi's Brain platform, a localisation system for items and assets that uses RFID and Bluetooth devices. Across 77 endpoints, the spec covers device and location management, key-value storage, presences and items, blob upload and download, events, and user-defined location rules - the core building blocks for tracking physical assets in a warehouse, retail, or logistics environment. Authentication can be a query API key, a header API key (X-API-Key), or a session cookie, and the base URL is templated per customer Brain instance.
Jentic publishes the only available OpenAPI specification for AWS IoT SiteWise, keeping it validated and agent-ready. AWS IoT SiteWise is a managed service that collects, organises, and analyses data from industrial equipment at scale. It models physical assets such as wind turbines, production lines, and chemical reactors as digital twins, ingests time-series property values from MQTT or OPC-UA gateways, and exposes the data through 73 endpoints covering assets, asset models, properties, gateways, portals, and dashboards. The service runs aggregations on the fly and supports SiteWise Monitor portals so operators can browse live and historical metrics without standing up custom dashboards.
Notehub is the Blues cloud service for managing cellular IoT devices built around the Notecard module. The API exposes projects, products, fleets, devices, events, routes, monitors, billing accounts, and usage data, letting integrators provision new devices, group them into fleets, push environment variables, and route incoming Notes to downstream cloud services. Authentication uses Bearer tokens obtained from /oauth2/token using a Personal Access Token or OAuth client credentials.
Jentic publishes the only available OpenAPI specification for Adafruit IO REST API, keeping it validated and agent-ready. The Adafruit IO REST API exposes the full IoT platform surface - feeds, dashboards and blocks, groups, throttle status, activities, charts, and signed-request authentication. The spec covers 71 endpoints and supports both header and query API key auth (X-AIO-Key) plus an X-AIO-Signature scheme for signed requests. Endpoints under /{username}/feeds include chart, batch, retain, previous, next, first, and last data accessors for finely controlled telemetry retrieval.
Adafruit IO is the cloud service paired with Adafruit's maker hardware, used to log sensor data, build dashboards, and trigger automations from connected devices. This REST API exposes feeds, dashboards, blocks, groups, triggers, tokens, ACL, throttle status, and webhook endpoints across 71 operations. Authentication uses the X-AIO-Key header (or query parameter) and an optional X-AIO-Signature for signed requests. The /{username}/groups/{group_key}/feeds/{feed_key}/data/batch path supports batched ingest scoped to a group, and the /{username}/triggers resource lets devices fire automations based on feed values.
Jentic publishes the only available OpenAPI specification for Adafruit IO REST API, keeping it validated and agent-ready. Adafruit IO is a hosted IoT platform built around named feeds, dashboards, blocks, and groups, and the full REST surface exposes 71 endpoints covering account info, throttle and activity inspection, feed and data operations, dashboard layout, and webhook-style triggers. It is the broadest programmatic surface on the platform and pairs with hobbyist hardware such as the Feather, QT Py, and Raspberry Pi over HTTP or MQTT.
The Ijenko IoE2 IoT API powers end-user IoT applications across smart energy, home automation, and connected devices. The /v3 surface exposes operations to manage accounts, places, users, devices, gateways, sensors, and metadata, plus historical sensor data, scenarios, and notifications. Authentication is via an Access-Token header or query parameter. The API is suited for utility companies, energy managers, and home automation providers that orchestrate large fleets of connected gateways and sensors.
With the smart-me REST API you get Access to all your devices in the smart-me Cloud and you can add your own devices. So its an easy way to add the smart-me Cloud support to your Hardware or Software Product. The API exposes 64 endpoints secured with basic authentication.
eDRV is a managed back-end for electric-vehicle (EV) charging networks. The v1 API exposes 57 endpoints that let operators provision charge stations, configure connectors, control charging sessions through remote-start and remote-stop commands, manage drivers and authorisation tokens, model locations and organisations, run reservations, and pull realtime telemetry, transactions, and statistics. It also includes vehicle telematics endpoints for battery, charge state, location, and odometer.
Jentic publishes the only available OpenAPI specification for Samsara API, keeping it validated and agent-ready. Track and manage commercial vehicle fleets, drivers, trailers, and industrial equipment through 56 endpoints covering real-time GPS locations, vehicle diagnostics, driver safety scores, Hours of Service (HOS) compliance, DVIRs, route planning, alert configuration, and webhook-based event notifications. The API serves fleet operators managing last-mile delivery, long-haul trucking, and field service operations.
The PAC Control REST API provides HTTPS access to variables and I/O tags running inside an Opto 22 SNAP-PAC-R or SNAP-PAC-S series industrial controller. It exposes the controller's strategy, letting external systems read and write integer, float, string, and table variables, plus analog and digital I/O points by name. Authentication is HTTP Basic Auth carrying an API key id and value, and JSON payloads are capped at 3KB to match the controller's onboard buffer.
Jentic publishes the only available OpenAPI specification for DataBoxEdgeManagementClient, keeping it validated and agent-ready. The Azure Data Box Edge management API exposes 49 operations across 32 paths to provision Data Box Edge devices, configure their bandwidth schedules, alerts, roles, shares, storage account credentials, triggers, users, and orders. Use it to onboard new edge appliances at branch sites, push compute roles and storage shares onto them, and monitor alerts across a fleet from a central control plane.
The Enphase Monitoring API gives developers access to live and historical telemetry from Enphase solar systems, including microinverters, batteries, and consumption meters. The v4 surface covers system discovery and search, device inventory, production and consumption meter readings, alarms and events, and billing-grade telemetry suitable for tariff and net-metering analytics. With 47 endpoints, it is one of the most detailed solar telemetry APIs available and is the canonical source of truth for Enphase-installed systems.
The Groupe PSA Connected Car B2B API gives fleet operators and approved B2B partners programmatic access to telemetry and management data for connected Peugeot, Citroen, DS, Opel, and Vauxhall vehicles. Across 47 endpoints it exposes vehicle characteristics, fleet rosters, last known position, telemetry, alerts, alarms, collisions, maintenance schedules, theft tracking, and remote callback monitors. The API uses HTTPS client-certificate authentication combined with a client_id query parameter, and is intended for cert-environment integration before promotion to production. Pagination is server-side via opaque tokens to keep requests stateless.
Jentic publishes the only available OpenAPI specification for openSenseMap, keeping it validated and agent-ready. openSenseMap is a citizen science platform for environmental sensor data - boxes (sensor stations) report measurements such as air quality, temperature, and humidity, and the API exposes them for both ingestion and analysis. Consumers can list and filter sensor boxes, query historical and recent measurements, retrieve descriptive statistics or interpolated values, and download data as JSON, CSV, or GeoJSON. Sensor owners can authenticate with a bearer token to register boxes, push measurements, and manage sensors.
Jentic publishes the only available OpenAPI specification for the Azure IoT Hub control plane (2019-07-01-preview), keeping it validated and agent-ready. The Microsoft.Devices/IotHubs resource provider creates and manages IoT Hub instances, their CA certificates, shared access keys, message routing, failover behaviour, and quota usage. It exposes 32 ARM endpoints to provision hubs, manage routing rules with $testall and $testnew dry-run paths, check routing endpoint health, list quota usage, and trigger manual failover.
Jentic publishes the only available OpenAPI specification for Ubidots IoT Platform API, keeping it validated and agent-ready. Ubidots is an IoT application platform that ingests sensor telemetry from connected hardware and lets developers build dashboards, alerts, and control loops on top of it. The 31-endpoint API covers device provisioning, variable management, time-series data ingestion and queries, organisations, events, and authentication tokens. Telemetry is posted per-device or per-variable, with last-value, raw-series, and aggregate queries available for charting and rule evaluation.
Jentic publishes the only available OpenAPI specification for Google Home, keeping it validated and agent-ready. The Google Home Local API exposes the local HTTP control surface used by the Google Home app to communicate with Google Home and Nest speaker devices on the same network. It covers device discovery, assistant readiness checks, alarms and timers, Bluetooth pairing, network setup, and supported locales and timezones. The endpoints are reverse-engineered from the Home app and require a cast-local-authorization-token retrieved from the Google account that owns the device.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.