API Ingress
The API Ingress page manages API-based integrations that feed data to the platform using external collectors or middleware. You use this path when running a Kudzu analytics agent — such as a Semtech UDP packet forwarder proxy or a Semtech LoRa Basics Station proxy — on your gateways or on your own premises.
Key areas#
API key list#
The main view shows existing API ingress keys with their names and creation dates.
Create API key#
Click Create API Key in the top-right corner to generate a new key. A dialog appears showing the generated key value and a field for an optional friendly name.
Copy the API key immediately — it cannot be accessed again after the dialog is closed.
Use cases#
API ingress keys support several integration patterns:
| Pattern | Description |
|---|---|
| Semtech UDP Packet Forwarder Proxy | A man-in-the-middle agent that runs on or near the gateway and forwards packet forwarder traffic to the platform |
| Semtech LoRa Basics Station Proxy | A similar proxy for Basics Station protocol gateways |
| Custom analytics integrations | Operators developing their own LNS or using custom ingestion solutions can feed data directly via the API |
Kudzu Analytics repository#
For custom integrations, documentation and examples are available at github.com/kudzu-technologies/analytics. The repository contains a gRPC endpoint definition, an example Go client, and an example packet forwarder.
How to use this view#
- Navigate to Configuration > API Ingress in the sidebar.
- Click Create API Key to generate a new key.
- Copy the API key immediately — it will not be shown again.
- Optionally give the key a friendly name and close the dialog.
- Use the API key to configure the Semtech UDP proxy, LoRa Basics Station proxy, or a custom integration client.
For more details on building custom integrations, see the Developer Reference.
Related pages#
- LNS Integrations — preferred high-quality data path
- HTTP Ingress — webhook-style HTTP endpoints
- Network — general network metadata and preferences