Useful Documents

• API Reference: https://docs.array.com/reference 
• API Flow Diagram: https://drive.google.com/file/d/1N6wIGmweseCxm6GxABHdy3YlEtodfBoc/view?usp=sharing 
• Credit Report API Flow: https://docs.array.com/docs/credit-report-api-flow 
• Postman Collection: https://docs.array.com/docs/postman-collection 
• OpenAPI/Swagger: https://docs.array.com/docs/openapiswagger 
• Customer SSO Flow Overview: https://docs.google.com/document/d/1de8VhYJZL6CMS2zm0xCGMXHqYte8_r-KbMD3YvRXVjA/edit?usp=sharing 

Base URL: https://sandbox.array.io

Client Authorization: The API does not require authentication

User Flow

This is the typical user flow using Array APIs:

1. See if the user is already enrolled in Array:

1. Do you have a clientKey for this user?

1. No - User must be enrolled and authenticated.

1. Display and obtain user consent.
2. Obtain the user’s information
3. Call Create User

1. Create User returns a permanent clientKey.

4. Store the clientKey - This is used the next time to verify that the user is already enrolled.
5. Call Retrieve Questions
6. Display authentication questions to the user
7. Call Submit Answers

2. Yes - User is already enrolled and authenticated. You may proceed to calling the desired APIs.

2. Call the desired API(s)
3. Listen for component and webhook events and respond accordingly.

---

Integration Workflow

This is the workflow for setting up Array API calls (see also the Array Web Component Flow Diagram):

1. Create User- A user must first be created in Array before they can access any Array features.

1. This is done only the first time a user accesses Array features.
2. The user must be prompted for and give their consent.
3. Create User can be called using existing user info, if you have it. Otherwise you will need to prompt the user to provide it before calling Create User.

1. https://docs.array.com/reference#create-user
2. Input

1. appKey (required)
2. First Name (required)
3. Last Name (required)
4. SSN (required)
5. Date of Birth (required)
6. Address (required)

1. Street Address
2. City
3. State
4. ZIP

3. Output

1. clientKey

4. Upon successful user creation, a permanent clientKey associated with the user is returned and must be stored. It is the existence of this clientKey which permits your system to determine whether a user needs to enroll in Array or not.

2. Authentication - A user must also be authenticated before they can access any Array features.

1. This is done only the first time a user accesses Array features.
2. The user will be authenticated by answering questions based upon their credit history.
3. Call Retrieve Questions to get the authentication questions.

1. https://docs.array.com/reference#retrieve-questions
2. Input

1. appKey (required)
2. clientKey (required)
3. provider1 (required)

3. Output

1. authToken
2. provider
3. questions[]

1. text
2. id
3. answers[] (for the user to choose from)

1. text
2. id        

4. Display the authentication questions to the user.
5. Get the user’s answers.
6. Call Submit Answers to answer the authentication questions.

1. https://docs.array.com/reference#submit-answers
2. Input

1. appKey (required)
2. clientKey (required)
3. authToken (required)
4. answers (required)

1. Key-value pairs of questionId-answerId returned by Retrieve Questions

3. Output

1. userToken

7. Upon successful authentication, a short-lived userToken associated with the user is returned. If this token expires during a user’s session, a new userToken can be obtained by calling Create User Token.

3. Call other API(s) for which you are subscribed.

1. Other APIs can now be called in a similar manner.

4. Listen for webhook events and respond accordingly

1. https://docs.array.com/docs/webhook-events 
2. Array sends webhook events to a listener that you have set up.
3. Credit alerts are sent out via webhook events.

1. https://docs.array.com/docs/efx-alerts
2. The "webhook" examples show how these alerts would appear from our events.
3. The titles of these alerts are customer-friendly explanations that you can include in the alert notifications (text message, email, etc) you send to the user.