# Create an answer to a question

Creates an answer to the question specified in the request URL by its ID.  Please note the following:  You must call this method for  in a question set. If the question has an  value of , then you must upload the documents using POST Create a document for a person or POST Create a document for a business. Solaris will not review the answers to the questions in the question set until  of them have been marked as ready_for_review. 

Endpoint: PATCH /v1/question_set/{question_set_id}/questions/{question_id}/answer
Version: 1.0

## Path parameters:

  - `question_id` (string, required)
    Solaris UID of question

  - `question_set_id` (string, required)
    Solaris UID of question set

## Request fields (application/json):

  - `response` (string)
    The answer text collected from the customer in your frontend.
    Example: "Here is my answer to the question"

  - `partner_notes` (string)
    Optional notes that you may add to the answer for Solaris to take into consideration.
    Example: "Optional notes"

  - `attachments` (array)
    An array of Solaris document IDs related to documents provided by the customer for the answer. Only required if the question has an  value of .
    Example: ["4c9464a1a29cbb5cf6090463ef7f49b9cdoc","876464a1a29cbb5cf6090463ef7f49a6cdoc"]

  - `ready_for_review` (boolean)
    Indicates whether the answer is ready for review by Solaris.  in the question set must have a value of  for this property before Solaris will review them.
    Example: true

## Response 200 fields (application/json):

  - `id` (string)
    ID of the question.
    Example: "1f0130f81d84ed3c75b32c428d5d7d93cqst"

  - `deadline` (string)
    UTC timestamp indicating the deadline for answering the question.
    Example: "2022-09-15T11:20:16.840208Z"

  - `question` (string)
    The question.
    Example: "Provide your annual KYC report."

  - `answer_type` (string)
    The type of answer required from the recipient.
    Enum: "TEXT_ONLY", "TEXT_AND_FILES"

  - `allowed_document_types` (array)
    Indicates the allowed document types that the recipient may provide (if the question has an  value of ).
    Enum: "ANNUAL_FINANCIAL_STATEMENT", "KYC_REPORT", "ID_DOCUMENT", "SIGNATURE", "PICTURE", "QES_DOCUMENT", "SIGNED_CONTRACT", "SIGNED_QES_DOCUMENT", "REGISTER_CHECK", "REGISTER_EXTRACT", "FOUNDATION_DOCUMENT", "SCHUFA_COMPACT_REPORT", "SCHUFA_GWG_REPORT", "SCHUFA_FULL_REPORT", "SCHUFA_SHORT_REPORT", "CREDIT_AGENCY_REPORT", "SHARE_HOLDERS_AGREEMENT", "SHAREHOLDERS_LIST", "TRADING_LICENSE", "TRANSPARENCY_REGISTER_EXTRACT", "INVOICE", "OTHER", "VIDEO"

  - `created_at` (string)
    UTC timestamp from when the question was created.
    Example: "2022-09-15T11:20:16.920885Z"

  - `updated_at` (string)
    UTC timestamp from when the question was last updated.
    Example: "2022-09-15T11:20:16.920914Z"

  - `answer` (object)
    Object containing data related to the recipient's answer.
    Example: {"response":"Here is my annual KYC report","partner_notes":"Optional partner notes","attachments":["4c9464a1a29cbb5cf6090463ef7f49b9cdoc"],"ready_for_review":true}

  - `answer.response` (string)
    The answer text provided by the recipient.
    Example: "Here is my annual KYC report"

  - `answer.partner_notes` (string)
    Optional partner notes regarding the answer.
    Example: "Optional partner notes"

  - `answer.attachments` (array)
    An array of Solaris document IDs related to documents provided by the recipient for the answer. Only required if the question has an  value of .
    Example: ["4c9464a1a29cbb5cf6090463ef7f49b9cdoc"]

  - `answer.ready_for_review` (boolean)
    Indicates whether the answer is ready for Solaris to review.
    Example: true

## Response 400 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `status` (string)
    Example: "400"

  - `code` (string)
    Example: "constraint_violation"

  - `title` (string)
    Example: "The request violated data integrity constraints"

  - `detail` (string)
    Example: "entity_id --> recipient id {entity_id} is invalid."

## Response 403 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `status` (string)
    Example: "403"

  - `code` (string)
    Example: "unauthorized_action"

  - `title` (string)
    Example: "Unauthorized Action"

  - `detail` (string)
    Example: "Unauthorized action is not allowed."

## Response 500 fields (application/json):

  - `id` (string)
    Example: "e8915041-9d8c-4d96-9dd1-04e8522ecdbf"

  - `status` (string)
    Example: "500"

  - `code` (string)
    Example: "generic_error"

  - `title` (string)
    Example: "Generic Error"

  - `detail` (string)
    Example: "There was an error."