The full Wildeye API documentation now lives at https://api.mywildeye.com/docs
Those docs are published by the API itself, so they are always current — including new endpoints and fields the moment they are released. This page is kept as a short introduction and points you there.
Overview
The Wildeye API lets you extract the time-series information recorded by your Wildeyes, along with information about what each series represents. It does not perform aggregation — totals and averages are calculated by the consuming application.
Base URL: https://api.mywildeye.com
The API is intended for developers who are comfortable with HTTP APIs and integration work. If you are unsure how to apply it, please talk to a developer before building against it.
Authentication
The API uses JWT bearer token authentication. An API key is generated in the Wildeye web interface by a client administrator, and controls which Clients, Groups, or Sites the key can read.
See Setting up API keys for how to create one.
Send the key as a bearer token:
Authorization: Bearer <your-token>
To check a key is being sent and accepted, call GET /api/v1/ping/auth — it returns 200 OK when the token authenticates.
What you will find in the documentation
https://api.mywildeye.com/docs contains both a written guide and the complete endpoint reference, with request and response examples you can try in the browser:
-
Getting started — authentication, and your first call.
-
Core concepts — sites, devices and archived sites, and which identifiers are safe to store long term.
-
Inputs, measurements and meter readings — the difference between logged sensor data and manually entered meter readings.
-
The query language — filtering by input id, measurement category, or device id.
-
Paging and reliable retrieval — page sizes, end-of-data signals, and safe retry behaviour.
-
Working with archived data — how to reach the historical readings of a site that has been archived or a device that has been redeployed.
-
Dates and timezones, data freshness, rate limits, errors, and integration recipes (including Power BI).
-
Full endpoint reference — every endpoint, parameter, and response schema.
Machine-readable specification
The current OpenAPI specification is always available at https://api.mywildeye.com/openapi/v1.json. Import that URL into Insomnia, Postman, or a client generator to get an up-to-date request collection.
Any Swagger or Insomnia files attached to this page are historical snapshots from earlier releases and are no longer maintained. Please use the OpenAPI URL above.