Dashboard overview

After signup, you'll land on the Overview page. Before you can start using Core Exchange, you need to complete your profile by providing some basic information about your institution. This includes:

• Verifying your email address
• Basic information about your institution
• Business information about your company
• Technical contact information

Once your profile tasks are complete, the Overview page will get you started on your journey to build your FDX-aligned API and launch your institution on Plaid's network.

• Conversion rate → Pre‑handoff user journey quality.
• Connection health → Post‑link data extraction reliability.
• Performance → Infrastructure characteristics observed by Plaid (availability and speed).
• Errors → Specific issues encountered during data extraction.

Integration health provides real-time error logs and health metrics for your Plaid integration. You can search and filter error logs to investigate and troubleshoot issues your customers are experiencing.

• What it measures — How often users who select your institution successfully complete account linking. This metric only covers activity after a user enters your institution's login flow and before control returns to Plaid (the “Handoff” step).
• Formula — (Number of successful user login attempts) / (Total number of user login attempts)
• Where it's evaluated — Conversion in the user flow is evaluated between Select institution → Handoff:

What it measures — The success rate of Plaid's data extractions from your API after an account has been linked. Unlike conversion rate, Connection health focuses on post‑Link activity and is evaluated at Token exchange and Data pulls.

Plaid sends two kinds of traffic to your API:

• User‑initiated traffic — Triggered when a user is actively going through a login or update flow. Account and transaction data are pulled in real time and made available to apps.
• Batch traffic — Scheduled, automated requests that keep financial data (e.g., transactions, balances) up to date even when the user isn't active.

• Success — Plaid did not encounter any errors during data extraction while interacting with your API.
• Error — Plaid encountered an error at any point during data extraction. While many errors come from non‑200 responses from your API, certain 200 responses can still be classified as errors if the extraction fails.

The proportion of successful API calls across your API's data resource endpoints:

(Number of successful API calls) / (Total API calls made)

• Uptime — Calculated as the percentage of successful and client‑error responses (HTTP 2xx, 3xx, and 4xx) out of all received responses, excluding scheduled downtime (as indicated by FDX 503 errors).
• Latency — The round‑trip response time when Plaid calls your endpoints from the us‑east‑1 (Virginia) region.

Click View all to see detailed logs of all errors encountered during data extraction.

The Institutions section enables you to configure your institution, which involves setting up Plaid's access to your API and establishing your institution's brand in Plaid Link.

There are three different institution configuration profiles that are available to you. Development and Staging can be configured to pre-production environments, allowing you to test them using the Validator. The Production configuration profile is designated only for your production environment.

Using the Brand Editor, you can configure your logo, institution name, and institution URL.

If you are a digital banking platform, then your Institutions section will have a slightly different view to support the many institutions that you might support as your customers.

The Validator section provides tools to test and validate your FDX API implementation. The Validator offers two testing modes: end-to-end validation and unit tests.

End-to-end validation runs a complete validation flow across all endpoints and accounts. Use end-to-end validation when:

• You are ready for the full validation required before Production.
• You need to validate how multiple endpoints work together across a complete workflow.

Unit tests allow you to run fast, targeted validations on specific FDX endpoints directly in the Dashboard, without running the full end-to-end validation flow. Use unit tests to validate API responses per endpoint and per account.

Unit tests perform:

• FDX schema checks via OpenAPI schema validation
• Plaid-specific validation rules used by the Validator

Unit tests do not:

• Validate the OAuth flow itself (OAuth is only used to obtain an access token)
• Replace the full Validator run (you must still pass a full end-to-end validation before Production)

Use unit tests when:

• You need rapid iteration on a specific endpoint or account.
• One account or endpoint is failing, but you want to continue testing others.
• You want clearer, rule-by-rule error messages to fix issues faster.
• You want to validate a specific account type, such as liability accounts (credit cards, loans, mortgages), to ensure type-specific fields and rules are correct.

To run unit tests:

1. In the Dashboard, open Validator and select unit tests.
2. Choose which environment to run against (Staging, Development, or Production).
3. Choose how to authenticate:
   • OAuth popup (recommended) — Connect a test account via OAuth. Use redirect URI https://dashboard.plaid.com/open-finance/redirect/oauth-callback.
   • Access Token — Paste a valid access token if OAuth is not yet working.
4. Select the accounts to test:
   • Let the Dashboard call /accounts to retrieve all accounts, or
   • Check Test against single account ID and paste an accountId to test a specific account.
5. Click Run Test.

Results display immediately. Each endpoint has its own Run button, so you can test endpoints individually without re-running the entire suite.

Unit tests support the following FDX v6 endpoints:

• /accounts
• /accounts/{accountId}
• /accounts/{accountId}/payment-networks
• /accounts/{accountId}/contact
• /accounts/{accountId}/transactions
• /accounts/{accountId}/statements
• /accounts/{accountId}/asset-transfer-networks

Note that /accounts is used to select an account but is not rule-tested in Unit Test mode. It either fails with a non-200 response (shown to you) or proceeds to account selection.

Each validation rule displays:

• Pass/Fail status
• Validation message explaining what was checked and why it failed

Example messages:

• Schema: "Field X is required by FDX v6."
• Plaid-specific: "accountMask must match last 4 digits of accountNumber."

Use these messages to fix your API responses, then re-run the specific endpoint or account immediately without rerunning the entire validation.

FDX schema validation ensures your JSON matches the FDX contract for that endpoint.

Plaid-specific validation rules verify that data can flow through Plaid's production API successfully. These checks validate the fields that Plaid extracts and uses for each product, ensuring your FDX responses contain the data structure Plaid expects.

The Validator performs the same checks as Plaid's production data extraction, including:

• Access token validity: Tokens must be active and not expired
• Date range formatting: Start and end dates must be in YYYY-MM-DD format with start date before end date
• Required field presence: Each product validates its core fields are present and properly formatted
• Data structure: Response objects match expected Plaid API schemas

For example, when validating /accounts/{accountId}/transactions, the Validator checks:

• Transaction name, amount, and date fields are present
• Amounts are numeric and properly formatted
• Pagination works correctly (Validator retrieves up to 500 transactions)

Validation scope: Only 200 responses are rule-validated. Non-200 responses show the failed call details instead.

For platforms managing multiple institutions, select the specific institution you want to test from the institution dropdown. Unit tests then behave the same as for a single Data Partner.

The Permissions Manager section allows you to:

• Search by customer to view authorization details of their connections
• View detailed API docs
• Set up webhooks to get real-time alerts each time a customer connects to or revokes access from a new application

The App Directory section displays details about the apps your customers are connected to, including categories and the number of connections. You can also view additional resources for the App Directory's FDX-aligned API.