# Create an approval for business identification Creates an additional final verification step to allow partners to approve or reject the business identification based on their internal compliance assessments. This is an optional endpoint for partners with this specific use case. Endpoint: POST /v1/businesses/{business_id}/identifications/{business_identification_id}/approvals 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. ## Request fields (application/json): - `approved` (boolean, required) The partner identification approval status. ## Response 200 fields (application/json): - `business_identification_id` (string) The unique ID of the business identification resource. Example: "4c74c804eaea5d2a2d64ef400a27a4d3bid" - `approved` (boolean) The partner approval status. Example: true ## 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"