Skip to main content
curl --request PATCH \
  --url https://{tenant_name}.{region}.techwolf.ai/taxonomy/skills/{skill_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "skill_description": "SQL is a standard database query language. The Skill \"SQL\" requires the ability to write and execute SQL queries.",
  "properties": {
    "sap_status": {
      "value": "active"
    }
  }
}'
This response does not have an example.

Authorizations

​
Authorization
string
header
required

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

Path Parameters

​
skill_id
string<uuid>
required

The universally unique ID of the Skill, consisting of alphanumeric characters, hyphens and underscores. The Skill name connected to this id can be identified by either using the Skill Search endpoint or in any response body that contains that Skill.

Required string length: 1 - 100
Example:

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

Query Parameters

​
external_vendor
enum<string>

The external vendor vocabulary in which the input Skills exist. This will only work for vendors that are activated on your tenant. If not passed, the input Skills have to be in the TechWolf vocabulary.

Available options:
workday,
sap_attribute_library
Example:

"workday"

Body

application/json
​
skill_description
string | null

Description of the Skill. Setting the Skill description to null will reset it to the default description provided by TechWolf. Please note that updating the description of a Skill within one Skill Cluster will apply that change across all other Skill Clusters containing the same Skill.

Example:

"SQL is a standard database query language. The Skill \"SQL\" requires the ability to write and execute SQL queries."

​
properties
object | null

Skill Properties give additional information about the Skill. These properties are the same over all occurrences of the Skill.

Example:
{ "sap_status": { "value": "active" } }

Response

No Content

⌘I