Application Pav1 - (legacy)

preapproval the information below is for the older api set please refer to application decisioning pav2 docid\ vwjhfefwgjkj9lggqlvw9 for the latest and greatest mpls perform due diligence for every loan request they receive an application can be submitted to the preapproval api whether or not it has been approved or denied if it hasn’t yet been approved, mpls can revise the loan application later after a decision was reached , approved , or denied (this includes rejected applications), in accordance with the fair lending law important to access the links below you must have the following ip addresses allowlisted sandbox 66 206 202 39 , 66 206 202 12 production 66 206 202 62 , 66 206 202 15 swagger https //lendingsandbox crbcos com/preapproval/swagger base url for sandbox https //lendingsandbox crbcos com/preapproval/v1 base url for production https //lending crbcos com/preapproval/v1 api scope for sandbox is coslending\ preapproval\ stg api scope for production is coslending\ preapproval\ prd the sandbox ui is https //lendingappsandbox crbcos com/preapproval/applications the production ui is https //lendingapp crbcos com/preapproval/applications api description application pav1 (legacy) /#post applicationsapprove post an application marked as approved application pav1 (legacy) /#postpreapprovalv2applicationsidattachments post file attachments to an existing application application pav1 (legacy) /#post applicationsdeny post an application marked as denied , with a declination object attached application pav1 (legacy) /#post application post an application without the decisioning application pav1 (legacy) /#post applicationsidapprove update an existing application to approved status application pav1 (legacy) /#post applicationsiddeny update an existing application to denied status notes during implementation, cross river and the mpl will agree on additional fields to be passed to cr based on the mpl's unique operating model during implementation, cross river and the mpl will also agree on the content of the data using the data dictionary monday board questions on specific fields should be posted there if you don't yet have access, contact your relationship manager (rm) data types and schemas are available directly in swagger, which is the "source of truth" mpls should send in their final decision using either post /approve or post /deny the rules that run when sending in the preapproval api, are informational they do not change the status of the application automatically cross river rules on preapproval when posting an application using the preapproval api, cross river checks the data against a set of regulatory rules and returns the rule results in the api response the rules run on the post /application call (known in the postman collection as non decisioned ) the rules will run on post /applications/approve as well the response body includes rule results in the rulesetresults object, which includes information about the rule and the data used when running the rule if one of the rules fails on preapproval, you can assume it will also fail in arix currently, there are no webhooks in preapproval the results of the rules are returned synchronously in the response cross river ops cannot manually override the result of a rule in pre approval pre approval rules do not alter the status of an application in pre approval sent in by an mpl the following is an example of a rulesetresults object that contains the cross river internal list rule "rulesetresults" \[ { "status" "success", "rulesprocessdate" "2023 09 06", "ruleresults" \[ { "ruleid" "92bc95b5 fa3c 468a b28b b06800bdb9d7", "version" "v1", "rulename" "internal list check", "ruledescription" "borrower information should not be on bank's internal list", "passed" true, "data" "anita loan 693952xxx,scrooge mcduck 014512994,unonx7enmokldcoxseauxw28serfp3xnelolpl2kopnzcq9n8y )}k;b,)sv8jco 78(yh^eu4|b ", "resultinfo" null } ], "preapprovalloanid" "693751f7 67ec 401a b945 b0750068734e" } ] data dictionary the data dictionary is presented to each mpl during the onboarding process the content to be sent will be agreed upon between cross river and the mpl before launch if you can't access the data dictionary, contact your rm post /applications/approve use this api to send in a unique application that hasn't been submitted already, and mark it as approved this is the preferred method for sending in an approved application for applications that were approved, but not accepted, you should use this api and mark acceptedbycustomer as false for applications that were approved and accepted by the customer, you should use this api and mark acceptedbycustomer as true the api returns a unique id that represents this application in our system if the decision changes afterwards, you can update it using post /applications/{id}/deny post /applications/deny use this api to send in a unique application that hasn't been submitted already, and mark it as denied this is the preferred method of sending in an application that has a final status of denied for denied applications, an applicationdeniedrequest object containing the reasons for denial, must be sent in along with the application information the api returns a unique id that represents this application in our system if the decision changes afterwards, you can update it using post /applications/{id}/approve post /application use this api to send in a unique application that hasn't been submitted already, and where a decision hasn't yet been made yet about the loan application we do not recommend this method of sending in applications unless you have a special use case that requires it the api returns a unique id that represents this application in our system when a decision is made, you can update it using post /applications/{id}/deny, post /applications/{id}/approve post /applications/{id}/approve use this api to approve an application that has already been submitted if the application is missing any required fields for an approved application, then send the complete application again this api only marks the application as approved and does not update other information no body is used in this call post /applications/{id}/deny use this api to mark as denied an application that has already been submitted an applicationdeniedrequest object containing the reasons for denial and other denial information must be submitted along with the application information important deprecated csv file to sftp folder for partners who onboarded before 2021, you should continue dropping application tapes into the sftp folder until you're ready to migrate to api the file format is csv naming convention mplid applicationtape yyyymmdd csv, where yyyymmdd is the date of file generation data in the report should be for prior day applications if a loan changes status (such as from denied to funded), you should include the updated loan record in the tape with the updatedflag the flag indicates that this record updates a previous credit decision for this loan post/preapproval/v2/applications/{id}/attachments this new preapproval api allows you to upload supporting files associated with an application and further improves our compliance practices important the zip file should contain the complete document package this includes the loan agreement aan credit report relevant documents or responses from vendors used to decision the application according to your credit underwriting policy as well as your bsa aml processes any data point used as input to your model for a list of acceptable attachment naming conventions, please refer to add loan documents docid\ urknihum7qylqdcee7tu the api is available in the latest postman collection and in the swagger documentation