Skip to main content
Create a new Skill Event for an Employee
curl --request POST \
  --url https://{tenant_name}.{region}.techwolf.ai/employees/{employee_external_id}/skill_events \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "external_id": "a3903505-eb84-42dc-a79f-5e7b1fe897b7",
  "event_type": "working_history",
  "timestamp": "2025-05-02",
  "content": {
    "job_title": "HR Manager",
    "start_date": "2018-09-05",
    "end_date": "2020-06-17",
    "company": "TechWolf BV",
    "job_description": "Manage the HR department and perform workforce planning"
  },
  "source": "employee-archives"
}
'
[
  {
    "title": "400 Bad Request",
    "description": "The request body was not structured correctly."
  }
]

Documentation Index

Fetch the complete documentation index at: https://developers.techwolf.ai/llms.txt

Use this file to discover all available pages before exploring further.

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<uuid>
required

Unique ID linked to an Employee, consisting of alphanumeric characters, hyphens and underscores. The unique ID in your system, consisting of alphanumeric characters, hyphens and underscores.

Required string length: 1 - 100
Pattern: [a-zA-Z0-9_-]+
Example:

"a3903505-eb84-42dc-a79f-5e7b1fe897b7"

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
Example:

"en"

​
strict
boolean
default:false

If strict is enabled, entity creation will fail when a Skill Profile cannot be constructed. If strict is set to false, failed Skill Profile creation will still result in entity creation, but the Skill Profile will be empty.

​
end_active_jobs
boolean
default:false

If enabled, any currently active working history Skill Event (i.e. one without an end_date) for this Employee will be ended automatically when the new Skill Event is created.

Body

application/json

Default structure of a Skill Event.

​
external_id
string<uuid>
required

The unique Skill Event ID in your system, consisting of alphanumeric characters, hyphens and underscores.

Required string length: 1 - 100
Pattern: [a-zA-Z0-9_-]+
Example:

"a3903505-eb84-42dc-a79f-5e7b1fe897b7"

​
event_type
enum<string>
required

Type of the Skill Event. Learn more about the Skill Event Types at How it works.

Available options:
working_history,
education_history,
resume_document,
learning,
feedback,
goal,
project,
ticket,
merge_request,
certificate,
skill_notes,
skill_profile_feedback
Example:

"working_history"

​
timestamp
required

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.

Example:

"2025-05-02"

​
content
working_history · object
required

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.

​
source
string<free text>

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

Example:

"employee-archives"

Response

No Content