April 2021
In April 2021 we added Go and Java code examples, added a nullable parameter, corrected parameter descriptions in the Direct Render PIN-Set Procedure, updated a field description for Get Savings Interest, added tutorial links to the Guides landing page, clarified email validation, updated the Customer ID Types enumeration, added two new Account Events messages, added some validation pages, and clarified some information in About Cards. Click April 2021 to see the details.
Go and Java code examples
We added code examples for Go and Java to the endpoint reference. Go to the Form Data section of any endpoint and click the tabs at the right for the desired code.
Added nullable parameter
The embossLine2 parameter of the Update Account endpoint is now nullable.
Parameter correction
The descriptions for the GGRBU and GGSAS parameters have been corrected in the Direct Render PIN-Set Procedure.
Update for interest_ytd field
interest_ytd fieldThe description for the interest_ytd field of the response schema for the Get Savings Interest endpoint was erroneous. It has been updated to clarify that it contains the interest paid during the specified period.
Added links to tutorials
We added links under About the API Guides to our Quickstart, Build a Sample App tutorial, and other getting-started guides so that they are easier to find. We also cross-linked these guides.
Email validation
For the email parameter we added information about validation: Marshmallow for the Python implementation and for the PHP implementation you should contact Galileo.
Customer ID Types enumeration updates
Some customer ID types require a timestamp in addition to the ID string, so we have updated the Customer ID Types enumeration with that information.
New Account Events
We added the ODCL: overdraft_credit_limit_change and ODGP: overdraft_start_grace_period Account Events.
Validation pages
For some endpoint parameters the validation information is too long to include in the individual parameter descriptions, so we have created a few pages for those validations, which we link to from the parameter descriptions:
About Cards clarification
The language in About Cards implied that there could be more than one active card per account. It now specifies that there should be only one active card per account, and also clarifies when the Add Card endpoint should be used.