How to connect to Plaid Exchange

The Plaid Exchange connector stores your bank-feed accounts and statements with Apideck's FDX data provider for Plaid Core Exchange. Connecting needs no Plaid credentials: Apideck sets up everything the connection needs when you enable it.

Prerequisites

• Access to the application's Vault, or an application that creates the connection for you through the Vault API.
• No Plaid account, API key, or OAuth app is needed to connect.

Steps

1. Enable the connection. Open Plaid Exchange in Vault and enable it, or have your application create the connection through the Vault API. There is no sign-in screen for you in Vault and nothing to paste.
2. Let Apideck provision it. Enabling the connection prompts Apideck to create a dedicated data space for it with Apideck's FDX data provider and to store the access credentials for that space on the connection. You never see or handle these credentials.
3. Wait for the connection to become ready. Apideck checks the connection's readiness. While provisioning finishes, the connection can stay in the added state (shown as Unauthorized in Vault) for a short time; this does not mean the connection failed, so do not delete it. Once the readiness check passes, the connection is callable.
4. Start sending data. Your application can now create bank-feed accounts and statements on this connection.

Notes

• No redirect URL. This connector has no OAuth flow, so there is no redirect or callback URL to configure.
• Disconnecting deletes the stored data. Deleting the connection removes its data space along with every account and statement stored in it. Only delete the connection when you no longer need that data.

Troubleshooting

• The connection stays in added (shown as Unauthorized in Vault). Provisioning can take a moment to complete, and the connection becomes callable as soon as the readiness check passes. If it stays in added (Unauthorized in Vault), contact Apideck Support with the connection ID rather than deleting it, because deleting the connection also deletes its stored data.
• Requests fail with an invalid-credentials error (401). The credentials stored on the connection were not accepted by its data space. Contact Apideck Support with the connection ID before deleting anything, because deleting the connection also deletes its stored data.
• Requests fail because the data space cannot be found (404). The connection's data space no longer exists even though the connection does. Delete the connection and enable it again to provision a new data space; nothing more is lost, because the old data space is already gone.