Here is the OpenAPI specification for our stable public endpoints.
Here is the OpenAPI specification for our stable public endpoints.
The identifier of the tenant where the target task, specified in the taskDefinition, will be stored or searched for. If not provided the domain's default tenant will be used. Ensure that the API user has the necessary permissions on the target tenant to create or update a task. If not, an error-response of type MISSING_PERMISSIONS
will be returned.
The task ID. This field should contain the task identifier used in the client's system.
The problem statement of the task.
Defines the type of the task. Can be used by deserialization tools to instantiate the correct sub-type.
The task title. If left blank, the taskDefinition.id
will be used as the title during implicit task creation or update.
The task language.
Context, such as background knowledge or additional information, required to solve the task.
curl -i -X POST \
https://api.taskbase.com/tasks/aspects/compute \
-H 'Authorization: Bearer <YOUR_UUID_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"tenantId": "product_123",
"taskDefinition": {
"id": "your_id_as_string",
"problemStatement": "When was the Battle of Waterloo?",
"type": "FREEFORM_TEXT"
}
}'
[ { "name": "Present 3rd person singular of regular verbs.", "description": "A learner can correctly form the present 3rd person singular of regular verbs.", "type": "CONCEPT", "aspectGroup": { … } } ]