import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/interview-drafts/topic-skills/"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/interview-drafts/topic-skills/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/interview-drafts/topic-skills/ \
--header 'Authorization: Bearer <token>'[
{
"id": "use_case_exploration",
"label": "Concrete cases",
"description": "<string>",
"selectable": true
}
]{
"error": "You do not have permission to perform this action."
}List guided-interview topic types
The topic types (skill_id values) a guided draft’s topics may carry, with the
human-facing label and one-line description the new-interview form shows in its
type picker. Admin only. selectable says whether a human may pick the type
in the form; non-selectable entries (custom_topic, i.e. “no skill”) are listed
so existing drafts can label what they carry. Fixed, unpaginated list.
import requests
url = "https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/interview-drafts/topic-skills/"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/interview-drafts/topic-skills/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));curl --request GET \
--url https://eu.app.clarifeye.ai/api/v1/projects/{project_id}/interview-drafts/topic-skills/ \
--header 'Authorization: Bearer <token>'[
{
"id": "use_case_exploration",
"label": "Concrete cases",
"description": "<string>",
"selectable": true
}
]{
"error": "You do not have permission to perform this action."
}Authorizations
Use Authorization: Bearer <token>. The token is either a user token / OAuth access
token, or a service-account API key (cfk_...). A key is valid on every endpoint and
acts as its service account, an organization member with per-store permissions.
Refused keys answer 403 with Invalid API key., API key revoked.,
API key expired. or API key disabled..
Path Parameters
UUID of the project