---
title: "Update device verification status for a user account"
method: PUT
path: "/programs/{programCode}/updateDeviceVerification"
tags: ["DeviceVerification"]
---

# Update device verification status for a user account

`PUT /programs/{programCode}/updateDeviceVerification`

Updates the device verification status for a user account.

## Path parameters

- `programCode` string, required

## Headers

- `X-GD-RequestId` string, required

## Request body

- UpdateVerificationRequest — Represents a request to update a device verification record or status. Contains the verification request key, event type, and related identifiers. Inherits standard request metadata from Gd.Bos.DataTransfer.Request.RequestBase.
  - `deviceVerificationRequestKey` integer, required — The unique key identifying the device verification request to update.
  - `eventType` 'GuestCheckOut' | 'Enrollment' | 'Login' | 'PreLoginCardActivation', required — The event type for device verification (e.g., GuestCheckOut, Enrollment, Login, PreLoginCardActivation). Uses Gd.Bos.DataTransfer.Enums.DeviceVerificationEventType to specify the verification scenario.
  - `accountIdentifier` string, nullable — The unique identifier for the account associated with the device verification.
  - `userIdentifier` string, nullable — The unique identifier for the user associated with the device verification.
  - `transferIdentifier` string, nullable — The unique identifier for the transfer associated with the device verification, if applicable.

## Response `200`

OK

- UpdateVerificationResponse — Represents the response returned after updating a verification record or status. Used to indicate the outcome of a verification update operation. Inherits standard response metadata from Gd.Bos.DataTransfer.Response.ResponseBase.
  - `responseDetails` ResponseDetail[], nullable — Required: A list of response details providing status codes, descriptions, and additional information about the result of the operation.
    - `code` integer — The primary status or error code for the response (e.g., 200 for success, 400 for validation error).
    - `subCode` integer, nullable — An optional subcode providing more granular detail about the response or error.
    - `description` string, nullable — A human-readable description of the response, error, or status.
    - `url` string, nullable — A URL linking to documentation or a web page with more information about the response code.

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/greendot/apis/baas-apis.md) · [All operations](https://skmtc.net/greendot/apis/baas-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/greendot/baas-apis/revisions/666553766b78/schema)