It is a software platform designed to accommodate the exchange of information between external software applications and the CU*BASE core processing system. This allows the financial institution to manage conversations with external vendors directly through their core processing solution, increasing efficiency versus accessing siloed software solutions.
The API system utilizes modern best practices associated with the REST API design paradigm. REST is a protocol designed to facilitate the creation, updating, reading, and deletion (CRUD) of remote data structures, referred to as an entity, over the HTTPS protocol. The request of these actions map to HTTP verbs specifying the entity via the URI.
Note: For security and regulatory reasons, CU*Answers does not adhere to HATEOAS.
The API utilizes HTTP Basic Authentication for access to the platform. Specific authorization is dictated by the unique ID provided during the transaction in the URL. These details are provided by the CU*Answers team during your integration.
Certain aspects of the API that relate to authentication, as well as identification within the core processing system require configuration for each partner. These items will not change for each CU you interact with, but will need to be provided with each transaction. 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 partner level:
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 differ based on the functionality you're using, but the following are always required:
| Action | HTTP Verb | Entity | URI | Documentation |
|---|---|---|---|---|
| Create | POST | Ready-to-Look Loan Application | /api/credit_unions/{CUID}/loans/applications | Docs |
| Retrieve | GET | Ready-to-Look Loan Decisions | /api/credit_unions/{CUID}/loans/applications/{unique_application_id}/decisions | Docs |
| Retrieve | GET | Member Search | /api/credit_unions/{CUID}/member_search | Docs |
| Create | POST | Ready-to-Book Loans | /api/credit_unions/{CUID}/loans | Docs |
| Create | POST | Ready-to-Service Loans | /api/credit_unions/{CUID}/service_loans | Docs |
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