---
title: "Post Talent Communication Preferences"
method: POST
path: "/v1/talent/{talentId}/communication-preferences"
tags: ["Talent"]
---

# Post Talent Communication Preferences

`POST /v1/talent/{talentId}/communication-preferences`

Adds or updates communication preferences for the specified talent.

## Path parameters

- `talentId` string, required

## Headers

- `RequestId` string, uuid — The unique request identifier used to correlate request data with log entries and events, formatted as a UUID.
- `FrontOfficeTenantId` integer
- `Tenant` string

## Request body

- TalentCommPreference
  - `id` integer — The identifier for the talent Communication Preference.
  - `talentId` integer, required — The identifier for the talent.
  - `email` boolean — The setting for the talent email preference.
  - `sms` boolean — The setting for the talent sms/text messaging preference.
  - `inApp` boolean — The setting for the talent in app notification preference.
  - `lastUpdated` string, date-time — The date and time for the talent last updated activity. The field follows the YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss formats and also supports fractional seconds, such as YYYY-MM-DDTHH:mm:ss.sss. For example, 2024-12-01, 2024-12-01T14:30:00, and 2024-12-01T14:30:00.546.

## Response `200`

The communication preferences for the specified talent.

- TalentCommPreference
  - `id` integer — The identifier for the talent Communication Preference.
  - `talentId` integer, required — The identifier for the talent.
  - `email` boolean — The setting for the talent email preference.
  - `sms` boolean — The setting for the talent sms/text messaging preference.
  - `inApp` boolean — The setting for the talent in app notification preference.
  - `lastUpdated` string, date-time — The date and time for the talent last updated activity. The field follows the YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss formats and also supports fractional seconds, such as YYYY-MM-DDTHH:mm:ss.sss. For example, 2024-12-01, 2024-12-01T14:30:00, and 2024-12-01T14:30:00.546.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Access Denied
- `404` — Not found
- `405` — Unsupported method
- `406` — Unsupported format(s) indicated by Accept header
- `415` — Unsupported format(s) indicated by the Content-Type header
- `429` — Too many requests
- `500` — An unexpected error occurred
- `502` — Service Unavailable
- `504` — Gateway Timeout

---

[API](https://skmtc.net/avionte/apis/aviont-partner-authorization-api.md) · [All operations](https://skmtc.net/avionte/apis/aviont-partner-authorization-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/avionte/aviont-partner-authorization-api/revisions/846b33e4e71b/schema)
