Invalid Input Errors

• /item/create was called directly, without using Link.

• Your user submitted incorrect micro-deposit amounts when verifying an account via Manual Same-Day micro-deposits.

• Access tokens are in the format: access-<environment>-<identifier>
• This error can happen when the access_token you provided is invalid or pertains to a different API environment

One of the account_id(s) specified in the API call's account_ids object is invalid or does not exist.

• Your integration is passing a correctly formatted, but invalid account_id for the Item in question.
• The underlying account may have been closed at the bank, and thus removed from our API.
• The Item affected is at an institution that uses OAuth-based connections, and the user revoked access to the specific account.
• The account_id was erroneously removed from our API, either completely or a new account_id was assigned to the same underlying account.
• You are requesting an account that your user has de-selected in the Account Select v2 update flow.

Ensure that your integration only uses account_id(s) that belong to the Item in question. Early on in your development it is important to verify that your integration only uses account_id(s), and other Plaid identifiers like item_id, for the Item that they belong to.

Also be sure to preserve the case of any non-numeric characters in Plaid identifiers, as they are case sensitive.

Either repeat the call you made that received this error without the optional account_ids object, or make a call to /accounts/get to return all of the current account_id(s) for the Item. You may then present this updated list of accounts to the user so that they may select which of their accounts they would like to use with your integration.

If the underlying account has not been closed or changed at the bank and the account_id no longer appears, Plaid may have removed the account entirely or assigned the account a new account_id, a situation known as "account churn".

Some common causes for account churn are:

• The Item was in an unhealthy state for an extended period of time. If an Item has remained in an error state for over a year, its underlying data may be removed. If the Item is then later refreshed, the Item data will be re-generated, resulting in new account_id data.
• The bank or user drastically changing the name of the account, e.g. an account named "Savings account" becomes "Jane's vacation fund".
• The account's mask is changed by the bank, which can occur when banks change their backend systems.

Account churn caused by the latter two reasons is unexpected API behavior. If you experience account churn on an Item that was otherwise healthy, file a Support ticket.

• The API keys are not valid for the environment being used, which can commonly happen when switching between development environments and forgetting to switch API keys

• You attempted to access an Asset Report using an audit_copy_token that is invalid or was revoked using /asset_report/audit_copy/remove or /asset_report/remove.

• The institution_id specified is invalid or does not exist.

• This error can happen when requesting to update account selections with a Link customization that does not enable Account Select v2.

• The link_token has expired. A link_token lasts at least 30 minutes before expiring.
• The link_token was already used. A link_token can only be used once, except when working in the Sandbox test environment.
• The link_token was created in a different environment than the one it was used with. For example, a Sandbox link_token was used in Production.
• A user entered invalid credentials too many times during the Link flow, invalidating the link_token.

For more detailed instructions on handling this error, see Handling invalid Link Tokens.

• The processor_token used to initialize Link was invalid.

• The endpoint you are trying to access must either be manually enabled for your account or requires a different pricing plan.
• The endpoint you are trying to access is for a product you did not collect consent for. This may be the case if you improperly migrated to Data Transparency Messaging
• Your integration is using a partner endpoint integration that has not yet been enabled in the Dashboard.
• Your integration is attempting to call a processor endpoint on an Item that was initialized with products that are not compatible with processor endpoints.

• For a returning user, Link was initiated with a product that is restricted from the pre-authenticated returning user flow, e.g. auth.

• Public tokens are in the format: public-<environment>-<identifier>
• This error can happen when the public_token you provided is invalid, pertains to a different API environment, or has expired.

After /processor/stripe/bank_account_token/create was called, Plaid received a response from Stripe indicating that the Stripe account specified in the API call's account_id is invalid.

• A request was made to /webhook_verification_key/get using an invalid key_id.
• The call to /webhook_verification_key/get was made from an environment different than the one the webhook was sent from (for example, verification of a Sandbox webhook was attempted against Production).

• A request was made to an Item created via the pre-authenticated returning user flow for a product that the Item was not initialized with during the original Link flow.

• Your user repeatedly submitted incorrect micro-deposit amounts when verifying an account via Manual Same-Day micro-deposits.

• You may not be enabled for the environment you are using.
• Your code may be calling a deprecated endpoint.

• The endpoint you are trying to access must be manually enabled for your account.

• The end user revoked access to their data via the Plaid consumer portal at my.plaid.com.