---
title: "Update User Data Collection Consent"
method: PUT
path: "/api/v1/admin/users/{user_id}/data-collection-consent"
tags: ["Admin APIs", "users"]
---

# Update User Data Collection Consent

`PUT /api/v1/admin/users/{user_id}/data-collection-consent`

Admin update of a user's data collection consent.

Deliberately separate from PUT /{user_id}: that route validates against
UserUpdate, which requires email/first_name/last_name, and treats their
presence as a profile change that gets pushed to Okta. Consent has nothing
to do with either, so it gets its own single-field route — the same split
the marketing-preferences routes above already use.

## Path parameters

- `user_id` string, required

## Request body

- UpdateDataCollectionConsent
  - `data_collection_consent` 'granted' | 'not-granted', required

## Response `200`

Successful Response

- DataCollectionConsentResponse
  - `data_collection_consent` 'granted' | 'not-granted', required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/carbonarc/apis/carbon-arc-client-admin-api.md) · [All operations](https://skmtc.net/carbonarc/apis/carbon-arc-client-admin-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/carbonarc/carbon-arc-client-admin-api/revisions/a8ca30023371/schema)