Financial Institutions

Financial Institutions

Quovo’s coverage extends to over 14,000+ financial institutions from around the world, and is not limited by institution or account type. We cover the full breadth of the financial services industry, including banks, brokerages, credit unions, and insurance companies.

Getting Our Institution List

To see a list of institutions covered by Quovo, send a GET request to https://api.quovo.com/v3/institutions. The response will include all institutions, with a set of fields for each institution listing.
curl -X GET \
	-H "Authorization: Bearer a724809d37d0a21b7e9257f45cee416f5aec61993ab4b09e" \

Response Fields

Response fields for an institution include an   id   that you’ll always need to include in your request to initiate a connection. Each institution also has a   name   field, which is what you should display in your app to help end users find their institution.
To retrieve a specific institution listing rather than all of our institutions, make a GET call to https://api.quovo.com/v3/institutions/{institution_id}
For each institution, you’ll also see an object called   access_details  . This tells you information that you should display to your users to help guide them in syncing a connection—such as   username_description  ,   passcode_description  , and   sync_notes  , which are special instructions helpful for connecting to a particular institution.
The /institutions endpoint also includes a   is_oauth   field for each institution to indicate whether specific institution’s connectivity is initiated via OAuth.
For a full set of /institutions fields, please see our reference docs 

Quovo Test Institutions

Quovo offers test institutions that simulate actual syncing workflows and live data from different types of accounts. You can get a full list of our test institutions in our data dictionary. Every test institution has an   id   just like our live institutions. Test institutions are denoted by the flag   is_test:true  .
If you’d like to get started with a straightforward “happy path,” then begin your testing with “Test Data – Bank,” which has an id of 21700, or “Test Data – Investment,” which has an id of 21534.
Our test institutions allow you to get a good sense of all of our connection sync flows, from simple to complex, as well as what different types of data and accounts look like on Quovo (e.g. bank vs credit card vs brokerage). The name of a test institution will tell you if it is a sync-flow test institution, an account type institution, or an institution that simulates a specific product such as autoverified deposits.
Requesting a New Institution
If you need an institution that’s not currently covered by Quovo, you can request a new connection by sending a POST call to https://api.quovo.com/v3/users/{user_id}/institution_requests. Your request should include:
  •   institution_name   – the name of the institution the end user would like to sync to
  •   institution_url   – the URL for the institution, preferably the full URL the end user actually visits to view their account data and not just the overall URL for an institution
  •   username   – the username the end user enters to log in to the institution
  •   passcode  – the passcode the end user enters to log in to the institution
We have a webhook that can alert you whenever someone requests a new institution. Learn more about all of our webhooks here.  
All of the information above is required because we’ll use it to initiate a new connection at the institution and attempt a sync. 
Note: Everything discussed in this section so far is handled automatically on the front-end by our Connect widget. Learn more about Connect here.
Here is a sample institution request:
curl -X POST \
    -H "Authorization: Bearer a724809d37d0a21b7e9257f45cee416f5aec61993ab4b09e" \
    -H "Content-Type: application/json" \
    -d '{"username": "testuser", "passcode": "testpw", "institution_name": "A Very Real Bank", "institution_url": "https://www.example.com/averyrealbank/index.html"}' \