Migrating to the Bloom Aggregator

The Bloom Aggregator is a component owned and maintained by Bloom. Previously, third party software was used to control aggregation. Presently, the Bloom Aggregator can import Plaid Processor Tokens via the Plaid Aggregator. In the near future, more aggregators will be supported.

Previously

Following the Enablement Services Getting Started guide, steps 1-6 are followed. Step 7 involves importing a processor token with the GraphQL mutation ImportConnections.

Bloom Aggregator with Plaid Processor Tokens

To use the Bloom Aggregator, call the GraphQL mutation ImportPlaidProcessorTokens. The input for this mutation is the same as ImportConnections. One should note, however, that the behavior and response of this mutation are different. When this mutation is called, Plaid Processor Tokens are imported independently. If one token fails, it does not block the import of the other tokens in the request. Two lists are returned - one with the connection information for the successfully imported tokens, and one for the tokens that failed to import alongside an error message for each one.

The remaining steps of the Getting Started guide can be followed after using ImportPlaidProcessorTokens in place of ImportConnections in step 7.

Disconnecting a Connection

The process for disconnecting a connection using a Plaid Processor Token is relatively the same.

1. Call the deleteConnection GraphQL mutation.
2. Using the access token associated with your plaid processor token, you may wish to call the Plaid item remove endpoint. This will invalidate the processor token.