A Ready-to-Service loan is an approved, underwritten, and booked loan that originates from a system external to the core processing platform. These generally are triggered by CU staff or third parties from an external LOS instead of the CU*BASE LOS. Ready-to-Service loan submissions are designed for the CU to be able to immediately start servicing the loan in the core system.
In order to interact with our API, you will see certain aspects in the sample documentation that are required to be different for each CU that you access. In all cases this information will be provided by the CU*Answers Software Integrations team, or retrieved from certain API endpoints. If you have any questions on how to acquire this information, please contact us.
These items are configured at the CU level:
When a loan is submitted to the system, a loan suffix is generated and a membership account is created if the request indicates necessary. In this scenario, the external party is expected to know whether the membership number being submitted is already existing, and is submitted for the correct member. Membership accounts are automatically generated through the use of this integration, provided the supplied member account is available in the core system
Action | HTTP Verb | Entity | URI |
---|---|---|---|
Create | POST | Loans | /api/credit_unions/{CUID}/service_loans |
Every verb is not supported to every entity. It is limited by permission and implementation, to be coordinated with your partner certification representative.
Submit Ready-to-Book loans that contain an approved decision (Typically underwritten in another system)
HTTP Verb | POST |
Endpoint URI | /api/credit_unions/{CUID}/loans |
Available Content-Type(s) | XML |
Request Body | View Schema View XML Sample |
Return Parameters | Variable length string Application ID |
HTTP Response on Success | HTTP 201 Created |
Response Body | View XML Sample |
This is a closed API, which means in order to gain access, you have to reach out. Also, if you have any questions that aren't covered in this documentation, or maybe they are and you'd like clarification, please Contact Us