http code 400
{
 "error_category": "INVALID_INPUT",
 "error_code": "INVALID_ACCOUNT_ID",
 "error_message": "Failed to find requested account ID for requested connection",
 "display_message": null
}

Common causes

• The account_id specified in the API call object is invalid or does not exist.
• 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 Connection in question.
• The underlying account may have been closed at the provider, and thus removed from our API.
• The account_id was erroneously removed from our API, either completely or a new account_id was assigned to the same underlying account.

Troubleshooting steps

• Verify that your integration is passing in correctly formatted and valid account_id(s)
• Ensure that your integration only uses account_id(s) that belong to the Connection in question. Early on in your development it is important to verify that your integration only uses account_id(s), and other Deck identifiers like connection_id, for the Connection that they belong to.
• Verify the Connection's currently active accounts and their account_id(s).
• Verify that the account_id was not changed or removed from the API.

Account churn

If the underlying account has not been closed or changed at the provider and the account_id no longer appears, Deck 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 Connection was in an unhealthy state for an extended period of time. If a Connection has remained in an error state for over a year, its underlying data may be removed. If the Connection is then later refreshed, the Connection data will be re-generated, resulting in new account_id data.
• The provider or user drastically changing the name of the account, e.g. an account named "Primary location" becomes "My home".
• The account's mask is changed by the provider, which can occur when providers change their backend systems.

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