---
title: "Create a Talent Activity"
method: POST
path: "/v1/talent/{talentId}/activity"
tags: ["Talent"]
---

# Create a Talent Activity

`POST /v1/talent/{talentId}/activity`

## Request

- Base URL: `https://api.avionte.com/front-office`
- URL: `https://api.avionte.com/front-office/v1/talent/{talentId}/activity`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Adds a talent activity record for the specified talent. The added activity is displayed on the *Activities* tab of the talent profile page.

## Path parameters

- `talentId` string, required

## Headers

- `RequestId` string, uuid: Unique request identifier in UUID format used to correlate request data to log entries and events.
- `FrontOfficeTenantId` integer
- `Tenant` string

## Request body

- TalentActivity
  - `typeId` integer, required: The identifier for the activity type.
  - `name` string: The name of the activity type.
  - `show_in` integer: An indicator of which activity type group the current activity type should be included in. Allowed values: -2 for Archived Activities/Tasks, -1 for All Activities/Tasks, 0 for Custom Tasks/Activities, 1 for Activities, 2 for Tasks. A value of -2 cannot be submitted when creating an activity.
  - `activityDate` string, date-time: The date of the talent's 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. If the timestamp includes a Z (e.g., YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ), it indicates UTC time. For example, 2024-12-01, 2024-12-01T14:30:00, 2024-12-01T14:30:00.546, 2024-12-01T14:30:00Z, and 2024-12-01T14:30:00.546Z.
  - `talentId` integer, required: The identifier for the talent.
  - `id` integer: The identifier for the talent activity.
  - `notes` string: The talent activity notes.
  - `userId` integer: The identifier for the user who logged the activity.

## Response `200`

The created talent activity.

- TalentActivity
  - `typeId` integer, required: The identifier for the activity type.
  - `name` string: The name of the activity type.
  - `show_in` integer: An indicator of which activity type group the current activity type should be included in. Allowed values: -2 for Archived Activities/Tasks, -1 for All Activities/Tasks, 0 for Custom Tasks/Activities, 1 for Activities, 2 for Tasks. A value of -2 cannot be submitted when creating an activity.
  - `activityDate` string, date-time: The date of the talent's 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. If the timestamp includes a Z (e.g., YYYY-MM-DDTHH:mm:ssZ or YYYY-MM-DDTHH:mm:ss.sssZ), it indicates UTC time. For example, 2024-12-01, 2024-12-01T14:30:00, 2024-12-01T14:30:00.546, 2024-12-01T14:30:00Z, and 2024-12-01T14:30:00.546Z.
  - `talentId` integer, required: The identifier for the talent.
  - `id` integer: The identifier for the talent activity.
  - `notes` string: The talent activity notes.
  - `userId` integer: The identifier for the user who logged the activity.

## 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.dev/avionte/apis/bold-front-office-api.md) - [All operations](https://skmtc.dev/avionte/apis/bold-front-office-api/llms.txt) - [OpenAPI document](https://skmtc.dev/avionte/apis/bold-front-office-api/revisions/bd5996cbaa0f?raw)