API development for CU*Answers is an important step in revolutionizing our ability to be flexible in providing data in a secure but streamlined manner, not only within the products we develop, but as a channel to allow others to develop products that connect with and integrate into the CU*Answers product suite. Once an API is developed, it can be used by other third-party applications, CU*BASE, It’s Me 247, Mobile Web, loan applications, or anything that we allow data access from now and in the future.
Ready to get started with APIs? Just follow these steps!
2: Release Credit Union Configuration to Development Environment
In order to get started CU*Answers Developer’s Help Desk requires some paperwork from the developer who intends to build off the APIs. These may be initially reviewed and then ordered via our DHD Online Store. However, prior to completing and returning the applicable paperwork, please schedule a first call with the DHD Help Desk to initially review your API project goals and desired outcomes. This early collaboration is very beneficial per our having a preliminary insight to your overall API scope, and providing additional assistance for proceeding.
Additionally, you may order the API Launch Kit to review and or complete the following documents:
- The Master API Access Agreement (signed per organization doing the API development; this may or may not be the credit union)
- The applicable Schedule(s) depending on the API type (signed per organization doing the API development; this may or may not be the credit union)
- Master Indemnification Agreement (signed by the Credit Union)
- Project Information Form – to describe your API project objectives and desired goals (completed per the organization doing the API development; this may or may not be the credit union).
Once fully executed, these documents get the process started for providing an initial API test development environment.
3: Select and Order Development API Set Keys
Once all necessary Agreements have been received by CU*Answers, you can proceed with requesting Development API (test) key sets. Depending on what you are creating, you will need access to some or all Development API key sets. It will be a CU*Answers determination for which API key (sets) may be provided and timing considerations. We recommend limiting your potential exposure by only selecting the API keys you actually need to fulfill the requirements of your project.
If you don’t see the API key you need, you can always sponsor the development of new Custom APIs. Visit the DHD website to learn more about Custom APIs.
Depending upon the Agreement/ Schedule(s) and other criteria, you will be provided a generic development API key to begin development against either a test CU*BASE credit union (e.g. Bedrock Test CU), or potentially, a real CU*BASE client configuration with staged settings and member data.
In order for live Member Information to be provided to a credit union’s API Developer, add the product shown to the right to your cart to receive the required Authorization to Release Member Information Form. This Authorization permits CU*Answers to create a test environment that closely matches your credit union’s CU*BASE production environment. Because this test environment could contain real data and CU*BASE configuration criteria, an authorized individual from the credit union must complete this Release Form, even if the developer is a credit union employee.
The developer should now have everything required to develop, test and demo to a client.
Normal timing: API test keys are normally delivered within 7-10 business days of order being received.
4. Schedule a Kick-Off Call
If this is your first CU*Answers API experience, the DHD will next schedule a video conference to more thoroughly review the overall API process, documentation, support access, Q&A, etc., to help ensure a smooth kick-off. This call is scheduled to closely coincide with receiving your Development API keys.
5. Order Testing Windows (optional)
Are you ready to test your API project? For situations in which your developer may desire an additional layer of testing to be performed, these pre-scheduled testing windows (normally 1-2 hours) allow developers to work directly with a DHD Account Executive to coordinate your testing with the CU*BASE functionality. This may include verifying the activities and configuration on the CU*BASE side, and additional items such as password complexity settings, first time sign-on considerations/ scenarios and user “lock-out” attributes.
Pre-scheduled testing windows typically require at least 2 weeks’ notice. Depending upon project testing needs, multiple testing windows may be required.
Cost: $200 per hour (1-hour minimum)
6. Select and Order Production API Set Keys
At least two weeks prior to launch, please order your Production API keys. These will allow your project to communicate with the API endpoints on the live production servers.
CU*Answers requires a unique client API key per each project, operating system and client. If you are developing Mobile App, you also must have a unique (separate) API key for iOS and Android versions. Please contact the DHD with additional questions.