How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

KPN LoRa Device Management API

KPN’s Low Power Long Range (LoRa) network service compliments existing 2G, 3G, 4G and LTE-M networks. It is based on the LoRaWAN protocol for Internet of Things (IoT).

KPN LoRa Device Management API is one of 38 APIs that KPN publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include IoT, LoRaWAN, and Device Management. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 19 operations across 13 paths, organized into 7 resource areas, and defines 33 schemas. It is described by OpenAPI 3.0.0, at version v1.2.

Requests are made against a single base URL, https://api-prd.kpn.com/data/lora/thingpark.

19 operations 13 paths 33 schemas 2 DELETE11 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v1.2
Base URL
https://api-prd.kpn.com/data/lora/thingpark
Authentication
OAuth 2.0
Terms of Service
Resource Areas
7

Authentication & Security 1

KPN LoRa Device Management API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials flow.

Paths & Operations 19

Across 13 paths, the API surfaces 19 operations — 2 DELETE, 11 GET, 4 POST, 2 PUT. They span 7 resource areas: Activation, Device, Subscription, Routing, Statistics, DeviceSecurity, Alarm. Each is listed below with its method, path, parameters, and response codes.

Activation 1
POST
/activate
Activates API
Activation 1 param body → 200400401403404429500
Device 6

Device operations provide the ability to manage ThingPark devices, device profiles, routing profiles, and connectivity plans.

GET
/devices
Retrieves devices
Devicesretrieval 8 params → 200400401403404429500
POST
/devices
Creates devices
Devicecreation 4 params body → 201400401403404429500
GET
/devices/{deviceRef}
Retrieves specific device
Deviceretrieval 2 params → 200400401403404429500
PUT
/devices/{deviceRef}
Updates specific device
Deviceupdate 4 params body → 200400401403404429500
DELETE
/devices/{deviceRef}
Deletes specific device
Devicedeletion 2 params → 204400401403404429500
GET
/deviceProfiles
Retrieves device profiles
Deviceprofilesretrieval 1 param → 200400401403404429500
Subscription 1
GET
/connectivityPlans
Retrieves connectivity plans
Connectivityplansretrieval 1 param → 200400401403404429500
Routing 5
GET
/routingProfiles
Retrieves routing profiles
Routingprofilesretrieval 2 params → 200400401403404429500
POST
/routingProfiles
Creates routing profiles
Routingprofilescreation 1 param body → 201400401403404429500
GET
/routingProfiles/{routingProfileRef}
Retrieves specific routing profiles
Routingprofileretrieval 2 params → 200400401403404429500
PUT
/routingProfiles/{routingProfileRef}
Updates specific routing profiles
Routingprofileupdate 2 params body → 200400401403404429500
DELETE
/routingProfiles/{routingProfileRef}
Deletes routing profiles
Routingprofiledeletion 2 params → 204400401403404429500
Statistics 2
GET
/deviceFrameStatistics
Retrieves frame statistics
Framestatisticsretrieval 6 params → 200400401403404429500
GET
/deviceHealthStatistics
Retrieves health statistics
Healthstatisticsretrieval 1 param → 200400401403404429500
DeviceSecurity 1

Device security operations provide the ability to manage AS keys and HSM groups for enhanced message encryption.

GET
/hsmGroups
Retrieves HSM groups
HSMgroupsretrieval 2 params → 200400401403404429500
Alarm 3

Alarm operations provide the ability to retrieve and acknowledge ThingPark device and base station alarms.

GET
/deviceAlarms
Retrieves device alarms
Devicealarmsretrieval 3 params → 200400401403404429500
GET
/deviceAlarms/{deviceAlarmRef}
Retrieves specific device alarm
Devicealarmretrieval 2 params → 200400401403404429500
POST
/deviceAlarms/{deviceAlarmRef}/acks
Acknowledges device alarm
Devicealarmacknowledgement 2 params → 201

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Device (28 properties), DeviceStatistics (22 properties), DeviceAlarm (16 properties), FrameStatistics (15 properties). Each schema is shown below with its type and property counts.

error
object
5 properties
AlarmStatistics
object
Resource representing a set of statistics related to alarms.
6 properties
AlarmThreshold
object
Resource representing a generic ThingPark alarm threshold.
3 properties
ApplicationSessionKeyRule
object
Resource representing a rule to indicate which application session key to use for each LoRa source port.
2 properties 1 required
CommercialDetails
object
Resource representing read-only commercial information about a device.
3 properties
ConnectivityPlan
object
Resource representing a ThingPark connectivity plan.
6 properties
Device
object
Resource representing a device created by a ThingPark subscriber.
28 properties
DeviceAlarm
object
Resource representing a device alarm.
16 properties
DeviceHealthStatistics
object
Resource representing read-only statistics about health states for devices.
4 properties
DeviceProfile
object
Resource representing a ThingPark device profile.
3 properties
DeviceStatistics
object
Resource representing read-only statistics for devices.
22 properties
FrameStatistics
object
Resource representing read-only statistics about radio frames for a device or a base station.
15 properties
HSMGroup
object
Resource representing an HSM group managed by ThingPark.
2 properties
ActivationReq
object
Thingpark Activation Credentials
2 properties
ActivationResp
object
1 property
Route
object
Resource representing a route of a ThingPark routing profile.
7 properties
RoutingProfile
object
Resource representing a ThingPark routing profile. Not available in ThingPark Enterprise versions, which rely on direct routes.
8 properties
ActivationType
string
Activation type of the device. Possible value is 'OTAA' (Over The Air Activation). 'ABP' (Activation By Personalization) is no longer possible in interface ver…
AlarmState
string
State of the alarm. Possible values are, by ascending order of criticity, 'CLEARED', 'UNCLEARED', 'WARNING', 'MINOR', 'MAJOR' and 'CRITICAL'.
ClassBState
string
Define the state of classB for the device. Possible values are 'ACTIVE' (Ready to be used) or 'INACTIVE' (Class B disable or not yet configured).
CommissioningState
string
Commissioning state of the device. Possible values are 'PERSONALIZED' (prepared but not yet registered on the network), 'COMMISSIONED' (prepared and registered…
CommunicationType
string
Communication type of Connectivity Plan : UNICAST, MULTICAST .
ContentType
string
Format of the routed payload. Possible values are 'XML' or 'JSON'. Default is 'XML' ('JSON' is supported starting from ThingPark 3.2).
DeviceClass
string
Define the class type of the device. A: Class A (Bi-directional end-devices with RIT), B: Class B (Bi-directional end-devices with synchronized receive slots),…
DurationOfInactivity
string
Duration of inactivity after which the alarm is raised. Possible values are '1HOUR', '2HOURS', '5HOURS', '10HOURS', '1DAY', '2DAYS', '4DAYS', '7DAYS' and '15DA…
HealthState
string
Health state of the device. Possible values are 'INIT', 'ACTIVE' or 'RFCNXERROR'.
healthState1
string
Level
string
Level of the alarm. Possible values are, by ascending order of criticity, 'ALL', 'WARNING', 'MINOR', 'MAJOR' and 'CRITICAL'.
LoraClass
string
LoRaWan class of the device.
MotionIndicator
string
Motion indicator configured for the device. Possible values are: 'NEARSTATIC', 'WALKINGSPEED', 'VEHICLESPEED' or 'RANDOM'.
ProcessingStrategyId
string
Id of a pre-defined data processing strategy. If set, it automatically configures relevant routing information for this device (and overrides existing routing…
Strategy
string
Strategy to use for routing to target addresses. Possible values are 'SEQUENTIAL' (try each target one after the other, stop after first success) or 'BLAST' (t…
Type
string
Type of frame. Possible values are 'UPLINK' or 'DOWNLINK'.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kpn-lora-device-management-openapi.yml Raw ↑

Other APIs KPN publishes across the network.

KPN Number Verify API
KPN SIM Swap API (Account Takeover Protection)
KPN Match API
KPN SMS API
KPN SMS Inbound API
KPN Mobile Services Management API
KPN FIAM API
KPN FIAM Eneco Data Products API
KPN Disturbance Check API
KPN Internet Speed Check API
KPN High Level Design FttX API
KPN SD-LAN / SD-WAN Network View API
Where this information came from

This is an independent, third-party profile of KPN LoRa Device Management API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.