For CU*Answers, API development represents an important process to continually enhancing our flexibility in providing data in a in a streamlined, secure manner. This is not only for the tools we develop, but provides a gateway to allow others to develop products that connect with and integrate into the CU*Answer product suite. Why is this process so important? For a variety of reasons… for instance, once an API is developed, it may be used by other 3rd party applications, CU*BASE, It’s Me 247 Online Banking, loan applications, or anything else we allow data access points in the future. As part of our efforts, and although each API situation may be a bit unique, here are the steps typically needed for completing an API process.
Consolidated steps to completing an API project:*
- Explore the DHD Online Store to review current APIs
- Visit the DHD site to review various API documentation
- If a custom API development request, we will assist you to complete and submit a Special Project Request/ Authorization form, and review applicable steps
- Contact the DHD Team to request applicable API Agreements
- Select and Order Development API (test) key sets
- Goal: deliver API test keys within 7-10 business days of order received
- Schedule a DHD team kick-off call to review project details
- Order pre-scheduled API Testing Windows (optional)
- An added layer of API testing with CU*Answers experts
- Select and order Production API key sets
- Contact CU*Answers to verify/ schedule API deployment
*Detailed explanation below
2: Visit our API Documentation Portal
This location will provide various API documentation to review. In most cases, this documentation should provide enough information for developers to begin estimating the programming effort required to integrate our APIs into your process. Some available materials:
- Select API Documentation
- Swagger APIs access
- Sample API Agreements (available per a DHD request)
Note: Per CU*Answers API development processes, APIs are not intended to be a one-time project you can walk away from… they will require constant monitoring and attention in accordance with new API updates/ modifications, CU*BASE releases, etc. Please review the CU*Answers Kitchen for CU*BASE Release and other larger topic projects in varying phases of development.
3: Releasing Credit Union configurations/ settings to an API development environment
CU*BASE provides an extremely comprehensive and flexible processing system for which clients are offered a wide variety of configuration options and settings. As a result, virtually every CU*BASE client is configured differently. For API developers, this often means that they may wish to perform development testing of an API specifically to a client’s data/ environment for CU*BASE has been configured vs. a CU*BASE test credit union (i.e. Bedrock). Depending upon who the developer may be (ex: an outside third party), API project type, desired test environment, etc. the Developer’s Help Desk will require various paperwork to be completed. In order to best determine which Agreements may be applicable, please schedule a call with the DHD to initially review your API project strategy and desired goals. This early collaboration is very beneficial per our gaining preliminary insight to your overall API project, providing additional assistance for proceeding and delivering the appropriate Agreements for your review. Common Agreements/ Forms include:
- 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).
- Master API Access Agreement – (signed per organization doing the API development; this may or may not be the credit union).
- 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)
Selecting the CU*BASE version on which to test against: Development of the CU*BASE system is an on-going process, with many features being enhanced or modified. In some cases, these modifications to the core may impact API features resulting in modifications needing to be made to the API and your corresponding app or project. Prior to starting API testing, we suggest you discuss these considerations with a DHD expert.
The development environment is accessible on the Internet and requires no additional special access.
The development environment will generally be available 24/7 with a short maintenance window each night. Additionally, the environment will be unavailable when new releases are rolled out until an update has been deployed. Visit the DHD site to view the latest Alerts/ News and other important information.
As previously mentioned, APIs will require on-going developer attention in accordance with new API updates/ modifications, CU*BASE releases, etc. Clients and developers must regularly check the DHD site for important API Updates, Alerts and News.
Note: As a reminder, all work we do for you is subject to the terms and conditions of the Client Master Services Agreement and/or the Master API Agreement between your organization and CU*Answers. CU*Answers may provide additional terms and conditions as based upon the services required.
4. Select and Order Development API Key Sets
Once all necessary Agreements have been fully executed, 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 applicable 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 potentially be provided to a credit union’s API Developer, you must execute an Authorization to Release Member Information Form. This authorization form 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 Authorization 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.
5. 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.
6. 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)
7. 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.
8. Launch Scheduling
Upon ordering your Production API Set Keys, it is between the client and developer to:
- Contact CU*Answers for scheduling a live date to our CU*BASE Production environment.
- Verify/ ensure your API matches a currently supported CU*BASE Release version.
- Provide us your planned timing (date) for releasing to Internet Stores (i.e. Apple).
Normal timing (for DHD reply back): Within 5 business days.