# Update user consents

Canonical page: https://docs.ovok.com/api/slim/user/update-user-consents

`POST /v1/slim/user/consents`

Updates one or more consents of the signed-in practitioner. Use it to save the answers of a combined consent prompt.

**Auth:** Bearer token for a practitioner session (the profile must be a `Practitioner`). The caller's access policy must grant `Consent:read`, `Consent:search`, `Consent:create` and `Consent:update` (a project admin who holds no access policy skips this check).
**Scope:** The caller's practitioner profile in the caller's project (from the token).

## Behaviour

- Send at least one of `medicalSettingsNotificationsConsent` and `termsAndConditionsConsent`. Only the fields you send change.
- `true` records acceptance of the currently published version of that consent. `false` withdraws it.
- A `termsAndConditionsConsent` change also creates, re-activates or revokes the legal `Consent` read by `GET /v1/me/consent/legal`.
- All changes commit together or not at all. Repeating the same values writes nothing.
- The consent answers of `/v1/me/consent/*` are refreshed right away.
- The response always carries the resulting state of every consent.


## Example

```bash
curl -X POST 'https://api.sandbox.ovok.com/v1/slim/user/consents' \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE3NjcyNjg4MDAsImV4cCI6MTc2NzI3MjQwMH0.Ql3B_ztDvctlyZ2z0vp4sl3ExXRQGkzmxdmTAqxNzZk' \
  -H 'Content-Type: application/json' \
  -d '{ "medicalSettingsNotificationsConsent": true, "termsAndConditionsConsent": true }'
```