Yodlee Error Reference

Some LinkMoney errors are analogous to common Yodlee errors. In general, these errors are thrown because something has gone wrong during an initial account link or during a routine data pull from an institution. Some Yodlee errors are user-facing and require user interaction to resolve. Others are development errors from misconfiguration. Still others are unexpected errors that can arise during the account aggregation process.

The Error Object

Schema

FieldTypeDescription
string

The error code follows the format YNNN. The error codes do not change. New error codes may be added as we introduce new features and enhance functionalities.

string

A descriptive message that explains the error scenario.

string

Unique Yodlee identifier used to troubleshoot issues at Yodlee's end.

Error Types

Error codes returned from Yodlee fall into one of the following categories:

  • API Authentication Errors
  • Validation Errors
  • Y400 Generic Errors
  • Y013 SAML Errors

Authentication Errors

The following authentication errors occur while accessing the API services.

API Authentication Errors

HTTP Status CodeError CodeError MessageCause and Action

Y001

loginName and password are required

You have not provided the login name or password to the cobrand (customer) login or user login services. Provide the valid login name and password.

Y002

Invalid loginName/password

You have provided an incorrect login name or password to the cobrand (customer) or user login services. Provide the valid login name and password.

Y003

Account is locked, contact Yodlee Customer Service

You have exceeded the allowed number of login attempts by passing an incorrect password seven consecutive times. The account is now locked. Your trial period of using Yodlee API services in the developer portal environment has ended. Contact Yodlee Customer Service.

Y005

Suspended user

The login name provided is for a suspended user. Contact Yodlee Customer Service.

Y006

Unregistered user

You have provided a user session for a user who has been unregistered from the system.

Y007

Authorization header missing

You have provided a user session for a user who has been unregistered from the system.

Y008

Invalid token in authorization header

Regenerate the admin access/user access token as the token you have provided is invalid or has expired. OR The cobSession/userSession you provided is invalid or expired. Regenerate the session token from login services.

Y009

Session tokens missing

You must provide the required authorization header parameter while invoking the API services. Refer to the authorization parameter recommendations.

Y010

Invalid session

The cobSession you provided does not belong to the cobrand (customer).

Y011

Invalid cobrand (customer) or incorrectly configured cobrand

Invalid configurations. Examples: PKI is not configured properly, vendor configurations are incorrect for asset classification data. Contact Yodlee Customer Service for details.

Y012

User session should not be passed

You have provided userSession to an API service that accepts only cobrandSession. Refer to the authorization parameter recommendations.

Y013

Fields should be passed as body parameters

You have provided the required fields to an API service as query parameters. Make sure that you pass them as body parameters.

Y014

Cobrand configuration missing

The required configurations seem to be missing in the backend. Contact Yodlee Customer Service.

Y015

Unauthorized user

This user is not authorized to access this endpoint.

Y016

{0} header missing

The endpoint cannot respond without the required header.

Y017

Your account is locked, contact Yodlee Customer Care

Your account is locked, contact Yodlee Customer Services.

Y018

Your trial/contract has expired; contact Yodlee Customer Care

Your trial period to use the Yodlee APIs in the developer portal environment has ended. Contact Yodlee Customer Services.

Y019

Issuer is either locked or deleted

You have provided an issuer or API key that is either locked or deleted.

Y020

Invalid token in Authorization header

The Authorization token is invalid. Create a new valid Access Token.

Y021

Maximum duration of token cannot be greater than {0} seconds

Yodlee sets the maximum duration of the token’s validity. The token’s expiry time minus the current time cannot be greater than the cobrand’s maximum token validity duration.

Y022

Configuration missing

The required configurations for this API endpoint are missing. Contact Yodlee Customer Services.

Y023

Token has expired

The Authorization token has expired. Create a fresh valid access token.

Y024

This API service is not relevant to be invoked for API Key based authentication

Invoking this API endpoint is not relevant for the API key-based authentication. If you are receiving this error, contact Yodlee Customer Service.

Y025

Invalid token. This endpoint does not accept a user-specific token. Provide a token without any user identifier

This cobrand-level API endpoint does not accept any user-specific tokens. Regenerate the token without passing any user identifier.

Y300

Invalid token

Regenerate the admin access/user access token as the token you have provided is invalid or has expired.

Y304

clientId and secret is locked. Contact Yodlee Customer Services

Your account is locked, contact Yodlee Client Services.

Y308

User registration service only works with admin token

You have provided the user access token to an API service that accepts only the admin access token.

Validation Errors

The following validation errors occur while accessing the API services.

Validation Errors

HTTP Status CodeError CodeError MessageCause and Action

Y301

Invalid clientId or secret

The client credentials you provided is invalid.

Y302

Missing header parameter {0},{1},{2},{3}

You are missing a required parameter. Review the API implementation notes to find the correct value.

Y303

clientId or secret is missing

You are missing a required parameter. Review the API implementation notes to find the correct value.

Y309

User already exists as an admin user, try registering user with different name

You have provided loginName that already exists as an admin user, try using a different name.

Y800

Invalid value for {0}

Review the parameter values passed. The parameter you provided is invalid. Reasons could be incorrect data type, deleted data, etc. Examples: Invalid value for status Invalid value for container Invalid value for loginName

Y801

Invalid length for {0}

The length of a parameter provided is not as expected. Review the API implementation notes to find the correct value. Example: Invalid length for description; min 3 and max 200 characters are allowed.

Y802

{0} not allowed

The parameter/value you provided is not allowed. Review the API implementation notes to find the correct value. Examples: categoryParam not allowed, future fromDate not allowed.

Y803

{0} required {1}

You are missing a required parameter. Review the API implementation notes to find the correct value.

Y804

Permitted values of {0} between {1} - {2}

The parameter value you provided is not in the acceptable range. Review the API implementation notes to find the correct value. Example: Permitted values are between 1 - 500.

Y805

Multiple {0} not supported

You can only provide a single value for this parameter. Review the API implementation notes to find the correct value.

Y806

Invalid Input

You have provided an invalid parameter name or JSON. Review the API implementation notes to find the correct value.

Y807

Resource not found

You have provided a resource value that does not exist in the system. Please check the URI you submitted for errors or invalid values. If the URI is correct, this may be a premium resource to which you need to subscribe. Ensure that you have previously authorized access to the resource through Yodlee Client Services.

Y808

Your password doesn't meet required criteria

The password you have provided to register or update credential services does not meet the required criteria. Ensure that the password value adheres to the eligibility criteria.

Y809

Invalid date range

The date range you have provided is invalid. Make sure the To date is greater than the From date and the range passed is within the acceptable limits.

Y810

{0} should not be same as {1}

You have passed the same values to at least two API input parameters. Examples: The new password should not be the same as the old password High Level categoryName should not be the same as categoryName

Y811

{0} value already exists

You have provided a parameter value that already exists. Ask the user to correct the value.

Y812

Required field/value - {0} missing in the {1}  

One of the mandatory parameter values is missing. Review the API implementation notes to find the correct value.

Y813

{0} should be provided

The request you made cannot be executed because the required information is missing from the request. Example: Either category or categoryId should be provided.

Y814

Exchange rate not available for currency

The exchange rate for the user's preferred currency is not available. Contact Yodlee Customer Service for details.

Y815

Cannot apply filter on {0} if {1}

The combination of query parameters you have provided is in error. Review the API implementation notes to find the correct values. Examples: Cannot apply filter on assetClassification. classificationType if assetClassification is not requested.

Y816

{0} can only be requested for {1}

The request you made is not applicable or relevant for a specific resource. Example: Credentials can only be requested for aggregated accounts.

Y817

Invalid JSON for {}

You have provided an invalid JSON as an input. Verify the JSON format and the field names. Example: Invalid JSON for transactionParam.

Y819

{0} cannot be updated

The parameter or resource you are trying to update is not supported for updates or cannot be updated. Examples: accountType cannot be updated account cannot be updated for this provider.

Y820

The {0} is not supported for {1} Note: 820 and 821 are similar type of errors with a slight variation in the error message

The combination of request parameters you have provided are not supported. Examples: The Type filter is not supported for insurance accountType while retrieving transaction The accountReconType field is not supported for container other than investment isAsset field is not supported for loan/card account type dueDate/frequency is not supported for bank/investment/otherAssets/otherLiabilities.

Y821

{0} not supported Note: 820 and 821 are similar type of errors with a slight variation in the error message

The data you requested is not currently enabled.

Y822

{0} cannot be requested for {1}

You have requested a piece of information that is not allowed. Example: Credential cannot be requested for a shared providerAccount

Y823

{0} not applicable {1}

You have requested a piece of information that is not relevant. Examples: Credentials are not applicable for real estate accounts Transaction are not applicable for reward

Y824

The maximum number of {0} permitted is {1}

You have provided data that is more than the permitted length. Example: The maximum number of accountIds permitted is 100. The maximum number of categoryIds permitted is 100

Y825

Update not allowed {0}

You have performed an operation that is not allowed. Examples: Update not allowed - Data Retrieval in Progress Update not allowed - Reason: REFRESHED_RECENTLY

Y826

Query parameter(s) {0} have been deprecated; support for them is only available through body parameters

You have provided the deprecated query input parameter. Make sure that you pass the relevant body parameters.

Y827

{0} has been reached. Please try later

The action you have performed has reached the threshold that is allowed for the day. Example: The maximum threshold for the day has been reached. Please try later

Y828

The provider has not yet requested the MFA information

You have provided the MFA details for an add/update account process that has not yet requested the information.

Y830

{0} has to be enabled {1}

The information that you are requesting cannot be provided, as the required dataset/feature is not enabled. Contact Yodlee Customer Services

Y831

Account already {0} for EBILL

You are trying to enroll or unroll EBILL for an ineligible account. Examples: Account already enrolled for EBILL Account already unenrolled for EBILL

Y832

Invalid syntax for {0}

The syntax you have provided for the input filter is invalid. Example: Invalid value(s) ACCT_PROFILES for dataset$filter

Y833

Invalid value(s) {0} for {1}

You have provided an invalid value for a filter. Example: Invalid syntax for dataset$filter

Y847

{0} cannot be requested, as {1} not enabled

You cannot request a feature-related attribute if the feature is not enabled. Example: isAssetTransferEligible cannot be requested, as SN 2.0 or asset transfer feature is not enabled

Y848

{0} cannot be provided as input, as the {1} feature is not enabled

You cannot update the attribute because the feature is not enabled. Example: DetailedCategoryId cannot be provided as input, as the detailed category feature is not enabled

Y850

Container: {0} are inactive. The accounts linked to them were deleted. Add the accounts again to reactivate them

You have deleted all available accounts under the container. Add the provider account again to restore them to the system. Example: Container: loan and investment are inactive. The accounts linked to them were deleted. Add the accounts again to reactivate them.

Y852

Duplicate {0} cannot be passed in the input

You cannot pass duplicate attributes in the input. Example: Duplicate ids cannot be passed in the input.

Y853

{0} parameters cannot be passed simultaneously

You cannot simultaneously pass similar parameters as input. Pass one parameter at a time while invoking the API. Example: dataset and datasetNames cannot be passed simultaneously.

Y854

The number of account additions have reached the maximum limit. Contact Yodlee Customer Services

You have exceeded the permissible number of accounts; no more can be added.

Y866

As the user edits the credentials, the initiatingSource value cannot be SYSTEM while submitting the user-edited credentials

You have provided incorrect value of initiatingSource as SYSTEM while submitting edit-credentials. Make sure you pass the relevant parameter as the user has edited the credentials.

Y867

As the user initiates the MFA refresh, the initiatingSource value cannot be SYSTEM while submitting the MFA information

You have provided incorrect value of initiatingSource as SYSTEM while submitting the MFA information. Make sure you pass the relevant parameter as the user initiates the refresh and provides the MFA information.

Y872

Maximum threshold to perform challenge deposit verification has been reached. No additional account verification is allowed

The number of challenge deposit verification (CDV) a consumer is allowed to perform in a lifetime is restricted to a certain threshold. Once that threshold has reached this error is shown.

Y400 Generic Error

Y400 is a generic error code that gets thrown for few functional or syntax validations that may occur while invoking the API services. If you facing this error and do not get the reason why the error is thrown, please contact Customer Services.

Y400 Generic Error

HTTP Status CodeError CodeError MessageCause and Action

Y400

{0}

You have not invoked the API service per our recommendations and implementation notes.

Y400

Credentials have to be encrypted

The PKI feature requires that you enter encrypted credentials and answers.

Y400

Accessibility denied

The API you called is not available in a sandbox environment. Example: You may be trying to register a new user on the developer portal environment.

Service Errors

Y9NN series errors are service level errors.

Service Errors

HTTP Status CodeError CodeError MessageCause and Action

Y901

Service not supported

The service you requested isn't available to you. Contact Yodlee Customer Services for details.

Y902

Oops some issue at our end

We're having technical difficulties connecting. Contact Yodlee Customer Services for details.

Y903

Connection unavailable

We're having technical difficulties connecting. Contact Yodlee Customer Services for details.

Y904

Internal exception

We're having technical difficulties. Contact Yodlee Customer Services for details.

Y013 SAML Error

Y013 error will be thrown by SAMLRegister and SAMLLogin services. A sub error code gets additionally returned for this error code. Sub error code has a unique error message associated with it.

Y013 SAML Error

HTTP Status CodeError CodeSub Error CodeError Message

Y013

001

Initiation failed

Y013

002

Encoding failed

Y013

003

Decoding failed

Y013

004

Invalid SAML configuration

Y013

005

Invalid user

Y013

006

Invalid source

Y013

007

Invalid source id for issuer

Y013

008

Invalid artifact

Y013

009

Invalid request

Y013

010

Invalid IssueInstant

Y013

011

Expired IssueInstant

Y013

012

IssueInstant is in future

Y013

013

Invalid response

Y013

014

Mismatched source

Y013

015

Invalid source for issuer

Y013

016

Invalid profile

Y013

017

Invalid assertion

Y013

018

Invalid assertion - NotBefore in future

Y013

019

Invalid assertion - NotAfter in past

Y013

020

Invalid statement AuthenticationInstant

Y013

021

Artifact generation failure

Y013

022

Artifact decoding failure

Y013

023

Invalid assertion length

Y013

024

Invalid assertion id

Y013

025

Duplicate assertion id

Y013

026

External exception

Y013

027

Source id generation failure

Y013

028

Request generation failure

Y013

029

Request generation XML failure

Y013

030

Request generation signature failure

Y013

031

Request verification signature failure

Y013

031

Response generation failure

Y013

032

Response generation failure - invalid SAML request

Y013

033

Response generation - XML failure

Y013

034

Response generation - invalid recipient

Y013

035

Response generation failure - invalid issuer

Y013

036

Response generation failure - invalid source id

Y013

037

Response generation - signature failure

Y013

038

Response generation failure - invalid SAML response info

Y013

039

Response generation failure - invalid subject

Y013

040

Response generation failure - invalid lifetime

Y013

041

Response generation failure - invalid artifact

Y013

042

Response generation failure - invalid assertion

Y013

043

Response generation failure - implementation library failure

Y013

044

Response generation failure - invalid source

Y013

045

Response generation encryption failure

Y013

046

Response verification xml failure

Y013

047

Response verification failure - invalid assertion

Y013

048

Response verification failure - invalid subject

Y013

049

Response verification failure - invalid statement

Y013

050

Response verification failure - invalid statement

Y013

051

Response verification failure - invalid certificates

Y013

052

Response verification failure - invalid SAML response

Y013

053

Response verification failure - decryption failure

Y013

054

Response verification failure - assertion verification failure, invalid certificates

Y013

055

Response verification failure - assertion verification failure, invalid id

Y013

056

Response verification failure - invalid issuer

Y013

057

Response verification failure - invalid source

Y013

058

Response verification failure - implementation library failure

Y013

059

Response restore failure - invalid SAML response

Y013

060

Response restore failure - invalid assertion

Y013

061

Response restore failure - invalid issuer

Y013

062

Response restore failure - invalid source

Y013

063

Response restore failure - certificate retrieval failure

Y013

064

Response restore failure - invalid subject

Y013

065

Response restore failure - invalid statement

Y013

066

Response restore failure - invalid confirmation method

Y013

067

Response restore failure - implementation library failure

Y013

068

No signing key found

Y013

069

Invalid subject confirmation

Y013

070

Invalid authentication statement instant

Y013

071

Response verification failure - invalid attributes encoding

Y013

072

Response verification failure - invalid assertion format

Y013

073

Response verification failure - assertion decryption

Y013

074

Response verification failure - invalid attributes format

Y013

075

Null SAML response

Y013

076

Failed to parse SAML XML response

Y013

078

Failed to restore SAML response

Y013

079

SAML internal system error

Y013

080

Invalid username

Y013

081

Null user credentials

Y013

082

SSO is not enabled or initialized

Y013

083

Null SAML credentials

Y013

084

Unknown Issuer ID null in SAML Credentials

Y013

085

Null issuer ID

Y013

086

Invalid issuer ID

Y013

087

Invalid SAML response type

Y013

088

Could not locate a valid Source for issuer

Y013

089

User not registered

Y013

090

The account for user is locked

Y013

091

Max user count

Y013

092

Invalid group name groupName

Y013

093

User Name already exists

Y013

094

userCredentials

Y013

095

samlResponse required

Y013

096

Issuer required

Y013

097

Source required

Y013

098

Failed to parse XmlStringElement type

Y013

099

Failed to parse XmlStringContent is not allowed in prolog

Y013

100

Failed to parse XmlStringXML document structures must start and end within the same entity

Y013

101

Failed to parse XmlStringA pseudo attribute name is expected

Y013

102

Failed to parse XmlStringContent is not allowed in prolog

Y013

103

Could not locate a valid source

Y013

104

Failed to parse XmlStringThe encoding declaration is required in the text declaration

Y013

105

User does not have any associated Issuer