Get Connected Devices List

This endpoint returns a list of devices that are currently connected to or have previously accessed the authenticated user's Netevia account. Each device entry includes identification details, connection status, and timestamps. Partners can use this data to surface device management features, enabling users to monitor for unauthorized access and maintain account security.

Endpoint

GET /settings/devices

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint to display a device management screen within your application, allowing users to see which devices are authorized to access their account. This is particularly useful for security dashboards or notification flows where users need to identify and act on unfamiliar devices. It can also be called periodically to audit connected devices or trigger alerts when new devices appear.

Response

200 OK

The response contains a top-level Devices array. Each element is either a base device object or an extended device object that includes additional status fields.

Base device fields (deviceInformationResponse):

Extended device fields (extendedDeviceInformationResponse — includes all base fields plus):

Top-level response object:

{
  "Devices": [
    {
      "deviceId": "d1a2b3c4-e5f6-7890-abcd-ef1234567890",
      "deviceName": "iPhone 15 Pro",
      "creationDate": "2024-08-10T09:15:00Z",
      "isDeleted": false,
      "isActive": true,
      "deletionDate": null
    },
    {
      "deviceId": "a9b8c7d6-e5f4-3210-fedc-ba9876543210",
      "deviceName": "MacBook Pro",
      "creationDate": "2024-07-01T14:22:00Z",
      "isDeleted": false,
      "isActive": false,
      "deletionDate": null
    },
    {
      "deviceId": "f0e1d2c3-b4a5-6789-0123-456789abcdef",
      "deviceName": "Chrome on Windows",
      "creationDate": "2024-06-15T11:00:00Z",
      "isDeleted": true,
      "deletionDate": "2024-09-01T08:30:00Z"
    }
  ]
}

Error Codes

Common Mistakes

• Not refreshing the Bearer token before calling this endpoint — tokens expire after 10 minutes, resulting in a 401 response.
• Assuming all items in the Devices array have the same shape — extended device objects include deletionDate and isActive fields that base objects do not; handle both variants in your response parser.
• Treating isDeleted: false as equivalent to isActive: true — a device can be registered but not currently active; use isActive to determine live session status on extended objects.
• Displaying raw deletionDate values without checking for null — always check for null before rendering deletion timestamps to avoid UI errors.

Related Endpoints

• DELETE /settings/devices/{deviceId} — Revoke access for a specific connected device
• GET /settings/profile — Retrieve account profile and security settings
• POST /api/auth/v2 — Obtain a new Bearer token for authentication
• POST /api/auth/refresh — Refresh an existing Bearer token before expiry

Example

curl -X GET https://api.banking.netevia.dev/settings/devices \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"