Documentation Index
Fetch the complete documentation index at: https://docs.owlintegrations.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The OWL DMS API provides a clean, reliable interface for accessing data from the OWL Mesh Network. Instead of dealing with the complexity of distributed data sources, you can use a single, consistent API to query and retrieve the information you need. This makes it easy to plug mesh-network data into your dashboards, analytics pipelines, or internal tools without needing to understand the underlying network architecture.Create API Key
Follow these steps to create your API key:- Log into your OWL DMS
- Navigate to
Settings>API Keys - Click on
New API Key - Fill in the details and click on
Create Key - OWL DMS will generate an API Key for you. Save the key for your application
Use API Key
Once you have your API key from the steps above, you can integrate it into your application. Here are some ways to use the API key to get access to your OWL Mesh data.Python Example
JavaScript Example
API Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
startDate | integer | Yes | Unix timestamp for the start of the data range |
endDate | integer | No | Unix timestamp for the end of the data range. If omitted, returns data up to the current time |
Use Unix timestamps (seconds since January 1, 1970) for the date parameters. You can convert dates to Unix timestamps using online converters or programming language utilities.
Data Format
Every request returns a JSON payload, where each entry is itself a JSON object representing an individual message from the mesh. No protocol wrangling. No decoding headaches. Just structured data delivered in a predictable format. Here is an example of how the retrieved data will look:Response Fields
| Field | Type | Description |
|---|---|---|
deviceId | string | Identifier of the device that reported this message |
timestamp | string | ISO 8601 timestamp when the message was received |
eventType | string | Type of event (e.g., “health”, “sensor”, “alert”) |
payload.hops | integer | Number of hops this message traveled through the mesh |
payload.Payload | object | Device-specific data including voltage, battery percentage, charging status, and temperature |
payload.DeviceID | string | Unique identifier of the originating device |
payload.duckType | integer | Type of device (e.g., 2 for standard duck) |
payload.MessageID | string | Unique message identifier |
Complete Example
Here’s a complete working example that fetches data from the last 24 hours:Support
Need help with the API?OWL IoT Discord Community
Get help from other developers
Email Support
Get direct support via email