Get Devices

The Get Devices endpoint retrieves a list of all devices associated with a specific user profile in the Netevia Banking platform. The response includes device names, identifiers, registration dates, and current statuses. This allows partners and users to audit connected devices and maintain control over account security.

Endpoint

GET /netevia/profile/{profileId}/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 when you need to display a user's registered devices within a banking application, such as on a security settings screen. It is also useful for auditing purposes — verifying which devices are active or have been removed from a profile. This endpoint supports device management workflows that help ensure only authorized devices retain access to a user's account.

Path Parameters

Response

200 OK

The response contains a Devices array. Each item in the array is a device object that may include the base fields (deviceInformationResponse) or extended fields (extendedDeviceInformationResponse).

Base device object (deviceInformationResponse)

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

{
  "Devices": [
    {
      "deviceId": "d1a2b3c4-e5f6-7890-abcd-ef1234567890",
      "deviceName": "iPhone 15 Pro",
      "creationDate": "2025-03-15T10:22:00Z",
      "isDeleted": false,
      "deletionDate": null,
      "isActive": true
    },
    {
      "deviceId": "a9b8c7d6-e5f4-3210-fedc-ba9876543210",
      "deviceName": "iPad Air",
      "creationDate": "2024-11-01T08:45:00Z",
      "isDeleted": true,
      "deletionDate": "2025-01-20T14:30:00Z",
      "isActive": false
    }
  ]
}

Error Codes

Common Mistakes

• Providing a profileId that does not exist or belongs to a different partner will return a 404 error.
• Using an expired Bearer token results in a 401 response; refresh your token via POST /api/auth/refresh before retrying.
• Expecting only base device fields — some items in the Devices array may include extended fields (deletionDate, isActive) depending on the device record; handle both shapes in your client code.

Related Endpoints

• POST /api/auth/v2 — Obtain a Bearer token for authentication.
• POST /api/auth/refresh — Refresh an expiring Bearer token.

Example

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