# Returns all relevant Aspects for a given task.

Endpoint: POST /tasks/aspects/compute
Version: 0.9.0
Security: bearerAuth

## Request fields (application/json):

  - `tenantId` (string)
    Example: "tenant_123"

  - `taskDefinition` (object)

  - `taskDefinition.id` (string, required)
    The task ID. This field should contain the task identifier used in the client's system.

  - `taskDefinition.type` (string, required)
    Defines the type of the task. Can be used by deserialization tools to instantiate the correct sub-type.
    Enum: "FREEFORM_TEXT", "IN_TEXT_FILL_IN_BLANKS", "IN_TEXT_CHOICES", "MULTIPLE_CHOICE", "MULTIPLE_RESPONSES", "SIMULATION"

  - `taskDefinition.language` (string)
    The task language.
    Enum: "DE_CH", "DE_DE", "EN_US", "EN_UK", "FR_FR", "IT_IT", "ES_ES"

  - `taskDefinition.title` (string)
    The task title. If left blank, the taskDefinition.id will be used as the title
            during implicit task creation or update.
    Example: "my_task_title"

  - `taskDefinition.problemStatement` (string, required)
    The problem statement of the task.
    Example: "When was the Battle of Waterloo?"

## Response 200 fields (application/json):

  - `name` (string)

  - `description` (string)

  - `type` (string)
    Indicates whether an Aspect represents a misconception (wrong aspect) or a concept (correct aspect).
    Enum: "CONCEPT", "MISCONCEPTION"

  - `aspectGroup` (object)
    The group to which the Aspect belongs.


## Response 400 fields

## Response 403 fields