curl --request PATCH \
  --url https://{tenant_name}.{region}.techwolf.ai/employees/{employee_external_id}/skill_events/{skill_event_external_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "timestamp": "2023-12-25",
  "source": "employee-archives",
  "content": {
    "start_date": "2018-09-05",
    "end_date": "2020-06-17",
    "company": "TechWolf BV",
    "job_title": "HR Manager",
    "job_description": "Manage the HR department and perform workforce planning"
  }
}'
This response has no body data.

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

​
employee_external_id
string
required

Unique ID linked to an Employee, consisting of alphanumeric characters, hyphens and underscores.

Required string length: 1 - 100
​
skill_event_external_id
string
required

Unique ID linked to a Skill Event, consisting of alphanumeric characters, hyphens and underscores.

Required string length: 1 - 100

Query Parameters

​
language
enum<string>
required

The language of the input data, which has an impact on the Skill extraction. auto will automatically detect the language used in the provided data.

Available options:
auto,
nl,
fr,
en,
de

Body

application/json

Update structure of a Skill Event.

​
timestamp

The completion date (in IS08601 format) of the Skill Event. From this point on, the Employee is considered to have obtained the Skills of this Event.

​
source
string

The source system of the Skill Event. This is used to keep track of where Skill Events originate from.

​
content
object

The content of the Skill Event. Each type of Skill Event has a different content. The content should align with the event_type. Expanding this field shows you the supported Skill Event content bodies.

Was this page helpful?

Get a Skill EventDelete Skill Event