---
title: "Invalidate device"
method: POST
path: "/users/{userId}/devices/{deviceId}/invalidate"
tags: ["devices"]
---

# Invalidate device

`POST /users/{userId}/devices/{deviceId}/invalidate`

Invalidate a user's device, treating it as if it were a new device on subsequent actions.

## Path parameters

- `userId` string, required
- `deviceId` string, required

## Response `200`

OK

- UserDevice
  - `userId` string, required — The ID of the user.
  - `deviceId` string, required — The ID of the device.
  - `createdAt` string, date-time, required — The time when the device was first created.
  - `authenticatedAt` string, date-time — The time when the device was last authenticated.
  - `invalidatedAt` string, date-time — The time when the device was invalidated.
  - `rememberedUntil` string, date-time — The time until which the device is remembered. While this timestamp is in the future, the `device.isRemembered` rules engine feature returns `true` for actions performed on this device.
  - `lastVerificationMethod` 'SMS' | 'AUTHENTICATOR_APP' | 'EMAIL_MAGIC_LINK' | 'EMAIL_OTP' | 'PUSH' | 'DEVICE' | 'SECURITY_KEY' | 'PASSKEY' | 'VERIFF' | 'IPROOV' | 'PALM_BIOMETRICS_RR' | 'IDVERSE'

## Other responses

- `401` — Unauthorized
- `404` — Not Found

---

[API](https://skmtc.net/authsignal/apis/call-connect-api.md) · [All operations](https://skmtc.net/authsignal/apis/call-connect-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/authsignal/call-connect-api/versions/5604d744e3ad/schema)