# Mark legal_identification as ready for review Updates the legal identification status from to and removes the flag. Call this endpoint after collecting and submitting the required documents and/or answers to the compliance questions from your customers to Solaris. Afterward, Solaris will review the submitted information and resume the legal identification process. Endpoint: PATCH /v1/businesses/{business_id}/identifications/{business_identification_id}/legal_identification/mark_as_ready Version: 1.0 ## Path parameters: - `business_id` (string, required) The unique business ID, generated after completing the business onboarding process. - `business_identification_id` (string, required) The unique ID of the business identification resource. ## Response 200 fields (application/json): - `id` (string) The unique ID of the business legal identification. Example: "14eb210435e09ab7f6a06c8b9b86ce27lid" - `identification_id` (string) The unique of ID the business identification resource. Example: "4c74c804eaea5d2a2d64ef400a27a4d3bid" - `business_id` (string) The unique business ID, generated after completing the business onboarding process. Example: "880bbac68a34add190786b9c74f4c82fcbiz" - `status` (string) The status of the business legal identification. Enum: "created", "information_required", "blocked_internally", "successful", "failed", "expired" - `reason` (string) The reasons for a failed legal identification. Example: "null" - `missing_information` (string) Missing information or documents that Solaris needs from the business to complete the legal identification process. Enum: "COMPLIANCE_QUESTIONS", "FOUNDATION_DOCUMENT", "OTHER", "REGISTER_APPLICATION", "SCHUFA_EXTRACT", "SCHUFA_GWG_REPORT", "SEALED_FOUNDATION_DOCUMENT", "SHAREHOLDERS_AGREEMENT", "SHAREHOLDERS_LIST", "SHAREHOLDERS_LIST_MOTHER_COMPANY", "SIGNED_FOUNDATION_DOCUMENT", "SOURCE_OF_FUNDS", "VAT_CERTIFICATE" - `missing_information_details` (string) Field that includes extra details or clarification on the missing information and/or documents Solaris requires. ## Response 400 fields (application/json): - `title` (string) Example: "Failed to build pagination headers." - `status` (string) Example: "400" - `id` (string) Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86" - `detail` (string) Example: "Cannot connect to database." - `code` (string) Example: "build_pagination_headers_failure" ## Response 403 fields (application/json): - `title` (string) Example: "Unauthorized Action" - `status` (string) Example: "403" - `id` (string) Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86" - `detail` (string) Example: "Unauthorized action is not allowed." - `code` (string) Example: "unauthorized_action" ## Response 500 fields (application/json): - `title` (string) Example: "Generic Error" - `status` (string) Example: "500" - `id` (string) Example: "e8915041-9d8c-4d96-9dd1-04e8522ecdbf" - `detail` (string) Example: "There was an error." - `code` (string) Example: "generic_error"