Migrate from Asset Reports to Base Reports

This guide will walk you through how to migrate from generating Asset Reports with Plaid's Assets product to generating Base Reports with Plaid Check's Consumer Report product.

1. To use Consumer Report, it is strongly recommended to update your Plaid client library to the latest version. The minimum required versions are:
   • Python: 23.0.0
   • Go: 26.0.0
   • Java: 24.0.0
   • Node: 25.0.0
   • Ruby: 29.0.0
2. Confirm that you have access to all required Plaid Check products in the Production environment. If you don't have access to Plaid Check, request access via the Dashboard. In order to migrate from Assets to Plaid Consumer Report, your end users must be in the US and you must be on a custom plan.

When using Plaid Check products, you must create a user prior to sending the user through Link, and you must initialize Link with the resulting user_token. This allows Plaid to associate multiple Items with a single user.

1. Call /user/create prior to creating a Link token
   • Include information about your user in the consumer_report_user_identity object
   • Store the user_id and user_token in your database
2. Update your call to /link/token/create
   • Include the user_token string from /user/create
   • Replace the assets product string with cra_base_report in the products array
   • Add a cra_options object and specify your desired days_requested
   • Include a consumer_report_permissible_purpose
3. (Optional) Unlike Assets, by default, Plaid Check includes only one linked Item per Report. To include multiple Items in a single Consumer Report, set enable_multi_item_link to true in the /link/token/create request.

const request: LinkTokenCreateRequest = {
  loading_sample: true
};
try {
  const response = await plaidClient.linkTokenCreate(request);
  const linkToken = response.data.link_token;
} catch (error) {
  // handle error
}

For more details, see the Plaid Check Implementation guide.

To enable an existing Assets-enabled Item for Consumer Report, call /user/create and /link/token/create as described above, but include the Item's access_token when calling /link/token/create. When Link is launched, the end user will go through the Consumer Report consent flow, and on successful completion of the flow, the Item will be enabled for Consumer Report.

Update your webhook listeners to listen for the new CHECK_REPORT_READY and CHECK_REPORT_FAILED webhooks.

• Upon receiving a CHECK_REPORT_READY webhook, you should call /cra/check_report/base_report/get, along with any other Consumer Report product endpoints that you would like to use.
• Upon receiving a CHECK_REPORT_FAILED webhook, you should call /user/items/get to determine why Items are in a bad state. If appropriate, send the user through Update Mode to repair them.

If you plan to continue using other Plaid Inc. products, such as Auth or Balance, you should continue to retrieve the public token and exchange it for an access token. If not, you no longer need to obtain an access token.

Asset Reports and Base Reports have similar but not identical schemas. This Google Sheet highlights their differences.

If you are using other Plaid Inc. products, note that the account_id returned in API responses from endpoints prefixed with /cra/ will not match the account_id returned in responses from non-CRA Plaid endpoints.