Create a new device
Create a new device and associate it with the current organization.
Middlewares: authMiddleware, validateBodyOrganization, validateOrganizationDelete
API key for authentication
In: header
Patient ObjectId
Paper ObjectId
Organization ObjectId
Response Body
application/json
curl -X POST "https://api.paperlesspaper.de/v1/devices/" \ -H "Content-Type: application/json" \ -d '{ "kind": "paper-display", "patient": "682fd0d7d4a6325d9d45b86d", "paper": null, "organization": "682fd0d7d4a6325d9d45b86e" }'{
"id": "682fd0d7d4a6325d9d45b86f",
"name": "Kitchen Display",
"serialNumber": "nrf-352656106701140",
"status": "online",
"createdAt": "2026-05-21T09:30:00.000Z",
"updatedAt": "2026-05-21T10:15:00.000Z"
}Query devices by user GET
Retrieve a paginated list of devices visible to the authenticated user. Either patient or organization is required. Middlewares: `authMiddleware`, `validateQuerySearchUserAndOrganization`
Deactivate Device DELETE
Admin-or-support, dry-run-first deactivation by epd DeviceId. Missing app records produce warnings and do not block IoT deactivation. An optional previousDeviceObjectId from the admin search allows orphaned paper assignments to be detached; without a known app id, papers remain unchanged. A dry run is the default and returns the papers currently attached plus a confirmationToken. Papers and their cross-paper references are preserved. To execute, repeat with dryRun=false and that token. After a confirmed IoT reset, cleanup can be retried with the same token without resetting the device again; a completed request returns its saved result. Cleanup only affects the original database device and detaches its remaining paper references. Change counts describe the successful cleanup attempt. Middlewares: `authMiddleware`, `validateAdminOrSupport`