---
title: "Verify device binding signature challenge"
method: PUT
path: "/v1/mfa/challenges/signatures/{id}"
tags: ["Device binding"]
---

# Verify device binding signature challenge

`PUT /v1/mfa/challenges/signatures/{id}`

Verifies the signature from a customer's device in order to verify their ownership of the device.  To create the signature: 1. Create a hash (SHA256) with the OTP/activation_code. 2. Sign the hash with the private key. 3. Encode the signature in `ASN.1` format. 4. Hex-encode the `ASN.1`-formatted signature. 5. Send the signature in the request body.

## Path parameters

- `id` string, required

## Request body

- object
  - `signature` string — The hex-encoded signature for the challenge.
  - `device_data` string — Any device-specific string provided by the calling client.

## Response `204`

Challenge successful

## Other responses

- `400` — Validation error
- `401` — Unauthorized
- `403` — No access
- `404` — Not found
- `409` — Conflict
- `500` — Internal server error

---

[API](https://skmtc.net/solarisgroup/apis/device-management.md) · [All operations](https://skmtc.net/solarisgroup/apis/device-management/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/solarisgroup/device-management/revisions/80dd46738839/schema)