---
title: "Create a Talent Work History"
method: POST
path: "/v1/talent/{talentId}/work-history"
tags: ["Talent"]
---

# Create a Talent Work History

`POST /v1/talent/{talentId}/work-history`

Adds details about the talent’s previous work experience. This information is displayed on the *Work History* tab of the talent profile.

## 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

- TalentWorkHistory
  - `workHistoryID` integer — The identifier for the talent work history record.
  - `talentId` integer, required — The identifier for the talent.
  - `company` string — The name of the company where the talent worked.
  - `title` string — The job title.
  - `from` string — The employment start date. This is an open-format text field containing the year, and possibly month of the date. For example, 2012, 9/12, 09-2012.
  - `to` string — The employment end date. This is an open-format text field containing the year, and possibly month of the date. For example, 2016, 5/16, 05-2016.
  - `city` string — The city of employment.
  - `state` string — The state/province or region of employment in open-format text.
  - `country` string — The country of employment in open-format text.
  - `duties` string — The duties the talent performed during employment.
  - `reason_For_Leaving` string — The reason for leaving.
  - `notes` string — Additional notes on the talent's work history.

## Response `201`

The work history for the specified talent.

- TalentWorkHistory
  - `workHistoryID` integer — The identifier for the talent work history record.
  - `talentId` integer, required — The identifier for the talent.
  - `company` string — The name of the company where the talent worked.
  - `title` string — The job title.
  - `from` string — The employment start date. This is an open-format text field containing the year, and possibly month of the date. For example, 2012, 9/12, 09-2012.
  - `to` string — The employment end date. This is an open-format text field containing the year, and possibly month of the date. For example, 2016, 5/16, 05-2016.
  - `city` string — The city of employment.
  - `state` string — The state/province or region of employment in open-format text.
  - `country` string — The country of employment in open-format text.
  - `duties` string — The duties the talent performed during employment.
  - `reason_For_Leaving` string — The reason for leaving.
  - `notes` string — Additional notes on the talent's work history.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Access Denied
- `404` — Not found
- `405` — Unsupported method
- `406` — Unsupported format(s) indicated by Accept header
- `409` — Operation could not be completed due to conflict.
- `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)