Glide

Glide supports seamless integration with Alkami Quick Apply, enabling members to open additional shares directly from Alkami’s online banking without needing to re-authenticate via Glide.

To enable the integration, follow these steps:

Provide Your Alkami Bank Identifier your Glide CSM

- Financial institutions (FIs) need to provide Glide with their Alkami Bank Identifier.
- If you are unsure where to locate this number, contact Alkami support for assistance.
- Example Format: <code>A1B2C3D4-E5F6-7890-ABCD-EF0123456789</code>

Obtain the Necessary File from Glide

- Glide’s Customer Success Manager (CSM) will provide you with the <code>init.Jarvis.sql</code> file.
- This file needs to be included in your SDK submission ticket to Alkami.

- Submit a Jira ticket to Alkami with the following details:
 - Type: SDK Submission
 - SDK Component Type: StandardSSO
- Attach the following to the ticket:
 - The <code>init.Jarvis.sql</code> file provided by Glide.
 - API URLs for staging and production environments. API URLs Format:
 - Append <code>/api/sso/alkami</code> to your regular URLs.
 - Example Staging URL: <code>https://mycu.meetglide.com/api/sso/alkami</code>
 - Example Production URL: <code>https://join.mycu.org/api/sso/alkami</code>

Sample SDK Submission Ticket Content Below is an example of what to include in your submission:

We recently implemented a new digital account opening platform with Glide. We would like to use the API to enable SSO, allowing members to transition from Quick Apply to the Glide platform seamlessly to open new shares, add joint accounts, or add beneficiaries. Currently, when redirecting members to Glide, they are required to re-enter their account number, SSN, and mobile number. This integration will eliminate the need for re-authentication when redirected from Quick Apply.

- Members may have multiple memberships (e.g., Personal, Joint, and Business).
- A member logs in to Alkami Online Banking and clicks on the Quick Apply widget.
- Alkami performs an SSO into Glide, redirecting the member to Glide’s select membership page.
- The member selects a membership and proceeds to Glide’s onboarding page.
- The member can add a new share.

- Staging URL: <code>https://mycu.meetglide.com/api/sso/alkami</code>
- Production URL: <code>https://join.mycu.org/api/sso/alkami</code>
- Attach the <code>init.Jarvis.sql</code> file to the ticket.

1. Provide Your Alkami Bank Identifier your Glide CSM
 - Financial institutions (FIs) need to provide Glide with their Alkami Bank Identifier.
 - If you are unsure where to locate this number, contact Alkami support for assistance.
 - Example Format: <code>A1B2C3D4-E5F6-7890-ABCD-EF0123456789</code>
 
2. Obtain the Necessary File from Glide
 - Glide’s Customer Success Manager (CSM) will provide you with the <code>init.Jarvis.sql</code> file.
 - This file needs to be included in your SDK submission ticket to Alkami.
 
3. Submit an SDK Submission Ticket
 - Submit a Jira ticket to Alkami with the following details:
 - Type: SDK Submission
 - SDK Component Type: StandardSSO
 - Attach the following to the ticket:
 - The <code>init.Jarvis.sql</code> file provided by Glide.
 - API URLs for staging and production environments. API URLs Format:
 - Append <code>/api/sso/alkami</code> to your regular URLs.
 - Example Staging URL: <code>https://mycu.meetglide.com/api/sso/alkami</code>
 - Example Production URL: <code>https://join.mycu.org/api/sso/alkami</code>
 
4. Sample SDK Submission Ticket Content Below is an example of what to include in your submission:
 
 We recently implemented a new digital account opening platform with Glide. We would like to use the API to enable SSO, allowing members to transition from Quick Apply to the Glide platform seamlessly to open new shares, add joint accounts, or add beneficiaries. Currently, when redirecting members to Glide, they are required to re-enter their account number, SSN, and mobile number. This integration will eliminate the need for re-authentication when redirected from Quick Apply.
 
 Quick Apply Flow:
 - Members may have multiple memberships (e.g., Personal, Joint, and Business).
 - A member logs in to Alkami Online Banking and clicks on the Quick Apply widget.
 - Alkami performs an SSO into Glide, redirecting the member to Glide’s select membership page.
 - The member selects a membership and proceeds to Glide’s onboarding page.
 - The member can add a new share.
 
 Include the following URLs:
 - Staging URL: <code>https://mycu.meetglide.com/api/sso/alkami</code>
 - Production URL: <code>https://join.mycu.org/api/sso/alkami</code>
 - Attach the <code>init.Jarvis.sql</code> file to the ticket.

Depending on the integration configuration desired, members can be directed to open up a new tab to apply for new shares via Glide or have Glide show as an iFrame within the Alkami experience. If you'd like to set this up as an iFrame, please mention your preference in your SDK submission ticket.

- Depending on the integration configuration desired, members can be directed to open up a new tab to apply for new shares via Glide or have Glide show as an iFrame within the Alkami experience. If you'd like to set this up as an iFrame, please mention your preference in your SDK submission ticket.

Overview

How It Works