---
title: "Set consent for a specific member"
method: PUT
path: "/members/{key}/consent"
tags: ["Members"]
---

# Set consent for a specific member

`PUT /members/{key}/consent`

Set consent for a specific member based on their key.
Note: Some consent types cannot be overridden — this method returns a 422 status code with a message when that happens.

## Path parameters

- `key` string, required

## Request body

- ConsentInput
  - `relationType` 'express-consent' | 'active-clients' | 'information-request' | 'business-card' | 'web-contacts' | 'purchased-list' | 'contest-participants' | 'mixed-list' | 'association-members' | 'employees' | 'partners' | 'inactive-clients', required — Accepted values: express-consent, active-clients, information-request, business-card, web-contacts, purchased-list, contest-participants, mixed-list, association-members, employees, partners, inactive-clients
  - `consentDate` string, nullable — Format Y-m-d
  - `consentProof` string

## Response `200`

The new consent attributes for the specified member

- ConsentDetails
  - `consentType` string
  - `relationType` string
  - `consentDate` string, nullable
  - `consentExpiration` string, nullable
  - `consentProof` string

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `404` — Member not found
- `422` — Unprocessable entity — consent cannot be overridden

---

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