Delete Connected Device

This endpoint removes a specific device that has been granted access to a user's account. Once deleted, the device can no longer authenticate or perform actions on the account, helping users quickly respond to theft, loss, or unauthorized access. In some implementations, removing a device also immediately terminates any active session on that device.

Endpoint

DELETE /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 when a customer reports a lost or stolen device, detects an unfamiliar device in their connected devices list, or simply wants to revoke access from a device they no longer use. Retrieve the target deviceId first by calling GET /settings/devices, then pass it in the request body to remove the device.

Request Body

{
  "deviceId": "d7e3f2a1-bc45-4d89-9f01-23456789abcd"
}

Response

200 OK

"Device successfully removed"

Error Codes

Common Mistakes

• Passing deviceId as a path parameter instead of in the request body — the OpenAPI schema defines deviceId as a required field in the JSON request body, not a path segment.
• Using an outdated or cached deviceId — always retrieve the current list from GET /settings/devices before calling this endpoint.
• Omitting the Content-Type: application/json header, which can cause the request body to be ignored or misread.
• Attempting to delete a device that has already been removed, which returns a 404 error.

Related Endpoints

• GET /settings/devices — Retrieve the list of all connected devices for the authenticated user
• POST /settings/devices — Register a new device for account access

Example

curl -X DELETE https://api.banking.netevia.dev/settings/devices \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "deviceId": "d7e3f2a1-bc45-4d89-9f01-23456789abcd"
  }'