---
title: "Verify Registration"
method: POST
path: "/v1/onboarding/registrations/device/verify"
tags: ["onboarding"]
deprecated: true
---

# Verify Registration

`POST /v1/onboarding/registrations/device/verify`

## Request

- Base URL: `https://api.4chems.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.4chems.com/v1/onboarding/registrations/device/verify`
- Auth: none required

> **Deprecated.**

Deprecated — use verify_device_login (same behaviour).

Poll a device-authorization challenge to token issuance (UC-075, RFC 8628).

Anonymous. While the human has not yet acted, answers 202
`{"status": "pending", "retry_after": <seconds>}` — sleep that many
seconds and call again with the same `challenge_id`. On approval,
answers 200 with Keycloak's token set (`access_token`, `refresh_token`,
`expires_in`, ...) handed over exactly once; every existing token-gated
tool then works unchanged with that `access_token`.

## Request body

- DeviceVerifyIn: Request body for POST /v1/onboarding/registrations/device/verify (UC-075).
  - `challenge_id` string, uuid, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/4chems/apis/platform-api.md) · [All operations](https://skmtc.dev/4chems/apis/platform-api/llms.txt) · [OpenAPI document](https://skmtc.dev/4chems/apis/platform-api/revisions/65e4f7b4dba0?raw)