---
title: "Create user consent for device monitoring"
method: POST
path: "/v1/persons/{person_id}/device_consents"
tags: ["Device Monitoring"]
---

# Create user consent for device monitoring

`POST /v1/persons/{person_id}/device_consents`

Records consent from the given person (specified in the request URL) to collect device fingerprints on their registered device. Each consent is tied to a specific device.

## Path parameters

- `person_id` string, required

## Request body

- DeviceConsent
  - `event_type` 'APPROVED' | 'REJECTED' — Indicates whether the customer approved or rejected device monitoring.
  - `confirmed_at` string — UTC timestamp from when the customer consented/refused to consent to device monitoring.

## Response `201`

Successful result of the operation

- SolarisServerDecoratorsDeviceConsent
  - `id` string — ID of the device consent.
  - `person_id` string — ID of the person that gave the consent.
  - `event_type` 'APPROVED' | 'REJECTED' — Indicates whether the customer approved or rejected device monitoring.
  - `confirmed_at` string — UTC timestamp from when the customer consented/refused to consent to device monitoring.
  - `created_at` string — UTC timestamp from when the consent event was created on Solaris' backend.

## Other responses

- `400` — You sent invalid data.
- `403` — You are not authorized to perform this action.
- `404` — Person with the given ID does not exists.
- `500` — Internal server error.
- `default` — Unexpected error

---

[API](https://skmtc.net/solarisgroup/apis/customer-identification-kyc.md) · [All operations](https://skmtc.net/solarisgroup/apis/customer-identification-kyc/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/solarisgroup/customer-identification-kyc/revisions/c481fa2414f9/schema)