Yodlee

opencollection: 1.0.0
info:
  name: Yodlee Core APIs
  version: 1.1.0
items:
- info:
    name: Transactions
    type: folder
  items:
  - info:
      name: Get Transactions
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/transactions'
      params:
      - name: accountId
        value: ''
        type: query
        description: Comma separated accountIds
      - name: baseType
        value: ''
        type: query
        description: DEBIT/CREDIT
      - name: categoryId
        value: ''
        type: query
        description: Comma separated categoryIds
      - name: categoryType
        value: ''
        type: query
        description: Transaction Category Type(LOAN, UNCATEGORIZE, INCOME, TRANSFER, EXPENSE or DEFERRED_COMPENSATION)
      - name: container
        value: ''
        type: query
        description: bank/creditCard/investment/insurance/loan
      - name: convertToCurrency
        value: ''
        type: query
        description: On-demand currency conversion parameter
      - name: detailCategoryId
        value: ''
        type: query
        description: Comma separated detailCategoryIds. The id of the detail category that is assigned to the transaction.
          This is a premium attribute which will be returned in the response only if the Detail Category feature is enabled.
          The supported values are provided by GET transactions/categories.
      - name: fromDate
        value: ''
        type: query
        description: Transaction from date(YYYY-MM-DD)
      - name: highLevelCategoryId
        value: ''
        type: query
        description: Comma separated highLevelCategoryIds
      - name: keyword
        value: ''
        type: query
        description: Transaction search text
      - name: skip
        value: ''
        type: query
        description: skip (Min 0)
      - name: toDate
        value: ''
        type: query
        description: Transaction end date (YYYY-MM-DD)
      - name: top
        value: ''
        type: query
        description: top (Max 500)
      - name: transactionSourceId
        value: ''
        type: query
        description: A unique ID that the provider site has assigned to the transaction
      - name: type
        value: ''
        type: query
        description: Transaction Type(SELL,SWEEP, etc.) for bank/creditCard/investment
    docs: The Transaction service is used to get a list of transactions for a user.<br>By default, this service returns the
      last 30 days of transactions from today's date when fromDate and toDate are not passed.<br>When fromDate and toDate
      are passed, the API will only return up to 2 years of transaction history. If the difference between fromDate and toDate
      is more than 2 years, API will return only last 2 years from the toDate.<br>The keyword parameter performs a contains
      search on the original, consume
  - info:
      name: Update Transaction for Transaction Source ID
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/transactions'
    docs: Update the category, consumer description, memo, isPhysical, merchantType, and detailCategory for a transaction
      by filtering it using the Transaction Source ID.<br>The HTTP response code is 204 (Success without content).<br>
  - info:
      name: Run Transaction Categorization Rule
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/transactions/categories/rules/:ruleId'
      params:
      - name: action
        value: ''
        type: query
      - name: ruleId
        value: ''
        type: path
        description: Unique id of the categorization rule
    docs: The run transaction categorization rule service is used to run a rule on transactions, to categorize the transactions.<br>The
      HTTP response code is 204 (Success with no content).<br>
  - info:
      name: Update Transaction Categorization Rule
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/transactions/categories/rules/:ruleId'
      params:
      - name: ruleId
        value: ''
        type: path
        description: ruleId
    docs: The update transaction categorization rule service is used to update a categorization rule for both system-defined
      category as well as user-defined category.<br>ruleParam JSON input should be as explained in the create transaction
      categorization rule service.<br>The HTTP response code is 204 (Success without content).<br>
  - info:
      name: Delete Transaction Categorization Rule
      type: http
    http:
      method: DELETE
      url: '{{baseUrl}}/transactions/categories/rules/:ruleId'
      params:
      - name: ruleId
        value: ''
        type: path
        description: ruleId
    docs: The delete transaction categorization rule service is used to delete the given user-defined transaction categorization
      rule for both system-defined category as well as user-defined category.<br>This will delete all the corresponding rule
      clauses associated with the rule.<br>The HTTP response code is 204 (Success without content).<br>
  - info:
      name: Get Transactions Count
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/transactions/count'
      params:
      - name: accountId
        value: ''
        type: query
        description: "Comma separated accountIds\t"
      - name: baseType
        value: ''
        type: query
        description: DEBIT/CREDIT
      - name: categoryId
        value: ''
        type: query
        description: Comma separated categoryIds
      - name: categoryType
        value: ''
        type: query
        description: Transaction Category Type(LOAN, UNCATEGORIZE, INCOME, TRANSFER, EXPENSE or DEFERRED_COMPENSATION)
      - name: container
        value: ''
        type: query
        description: bank/creditCard/investment/insurance/loan
      - name: detailCategoryId
        value: ''
        type: query
        description: Comma separated detailCategoryIds. The id of the detail category that is assigned to the transaction.
          This is a premium attribute which will be returned in the response only if the Detail Category feature is enabled.
          The supported values are provided by GET transactions/categories.
      - name: fromDate
        value: ''
        type: query
        description: Transaction from date(YYYY-MM-DD)
      - name: highLevelCategoryId
        value: ''
        type: query
        description: Comma separated highLevelCategoryIds
      - name: keyword
        value: ''
        type: query
        description: "Transaction search text\t"
      - name: toDate
        value: ''
        type: query
        description: Transaction end date (YYYY-MM-DD)
      - name: type
        value: ''
        type: query
        description: Transaction Type(SELL,SWEEP, etc.)
    docs: The count service provides the total number of transactions for a specific user depending on the input parameters
      passed.<br>If you are implementing pagination for transactions, call this endpoint before calling GET /transactions
      to know the number of transactions that are returned for the input parameters passed.<br>The functionality of the input
      parameters remains the same as that of the GET /transactions endpoint.<br>If the difference between fromDate and toDate
      is more than 2 years, API will
  - info:
      name: Get Transaction Categorization Rules
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/transactions/categories/txnRules'
    docs: The get transaction categorization rule service is used to get all the categorization rules.<br>
  - info:
      name: Delete Category
      type: http
    http:
      method: DELETE
      url: '{{baseUrl}}/transactions/categories/:categoryId'
      params:
      - name: categoryId
        value: ''
        type: path
        description: categoryId
    docs: The delete transaction categories service is used to delete the given user-defined category.<br>The HTTP response
      code is 204 (Success without content).<br>
  - info:
      name: Get Transaction Category List
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/transactions/categories'
    docs: The categories service returns the list of available transaction categories.<br>High level category is returned
      in the response only if it is opted by the customer.<br>When invoked by passing the cobrand session or admin access
      token, this service returns the supported transaction categories at the cobrand level. <br>When invoked by passing the
      cobrand session and the user session or user access token, this service returns the transaction categories <br>along
      with user-defined categories.<br>Dou
  - info:
      name: Create Category
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/transactions/categories'
    docs: The create transaction categories service is used to create user-defined categories for a system-defined category.<br>The
      parentCategoryId is the system-defined category id.This can be retrieved using get transaction categories service.<br>The
      categoryName can accept minimum of 1, maximum of 50 alphanumeric or special characters.<br>The HTTP response code is
      201 (Created successfully).<br>
  - info:
      name: Update Category
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/transactions/categories'
    docs: The update transaction categories service is used to update the transaction category name<br>for a high level category,
      a system-defined category and a user-defined category.<br>The renamed category can be set back to the original name
      by passing an empty string for categoryName.<br>The categoryName can accept minimum of 1, maximum of 50 alphanumeric
      or special characters.<br>The HTTP response code is 204 (Success without content).<br>
  - info:
      name: Get Transaction Categorization Rules
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/transactions/categories/rules'
    docs: The get transaction categorization rule service is used to get all the categorization rules.<br>
  - info:
      name: Create or Run Transaction Categorization Rule
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/transactions/categories/rules'
      params:
      - name: action
        value: ''
        type: query
        description: To run rules, pass action=run. Only value run is supported
      - name: ruleParam
        value: ''
        type: query
        description: rules(JSON format) to categorize the transactions
    docs: 'The Create or Run Transaction Categorization Rule endpoint is used to: <br>Create transaction categorization rules
      for both system and user-defined categories.<br>Run all the transaction categorization rules to categorize transactions
      by calling the endpoint with action=run as the query parameter. <br><br>The input body parameters to create transaction
      categorization rules follow:<br>     categoryId - This field is mandatory and numeric<br>     priority - This field
      is optional and numeric. Prio'
  - info:
      name: Get Transactions using Transaction ID
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/transactions/:transactionId'
      params:
      - name: container
        value: ''
        type: query
        description: bank/creditCard/investment/insurance/loan
      - name: convertToCurrency
        value: ''
        type: query
        description: On-demand currency conversion parameter
      - name: transactionId
        value: ''
        type: path
        description: An unique identifier for the transaction. The combination of the id and account container are unique
          in the system.
    docs: The Transaction service is used to get a list of transactions for a user using Transaction ID.<br>
  - info:
      name: Update Transaction
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/transactions/:transactionId'
      params:
      - name: transactionId
        value: ''
        type: path
        description: transactionId
    docs: The update transaction service is used to update the category,consumer description, memo, isPhysical, merchantType,
      detailCategory for a transaction.<br>The HTTP response code is 204 (Success without content).<br>
- info:
    name: Accounts
    type: folder
  items:
  - info:
      name: Associated Accounts
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/accounts/associatedAccounts/:providerAccountId'
      params:
      - name: providerAccountId
        value: ''
        type: path
        description: providerAccountId
    docs: Yodlee classifies providers into credential-based aggregation and Open Banking (OB) providers.<br>This service is
      associated with the OB aggregation flow. As part of the OB solution, financial institutions may merge their subsidiaries
      and provide data as a single OB provider.<br>Before the OB solution, this data was aggregated with different provider
      IDs.<br>This service accepts the providerAccountId and returns all accounts of the associated providerAccounts that
      belong to the subsidiary of the
  - info:
      name: Get Accounts
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/accounts'
      params:
      - name: accountId
        value: ''
        type: query
        description: Comma separated accountIds.
      - name: container
        value: ''
        type: query
        description: bank/creditCard/investment/insurance/loan/reward/realEstate/otherAssets/otherLiabilities
      - name: convertToCurrency
        value: ''
        type: query
        description: On-demand currency conversion parameter
      - name: include
        value: ''
        type: query
        description: profile, holder, fullAccountNumber, fullAccountNumberList, paymentProfile, autoRefresh<br><b>Note:</b><br><li>fullAccountNumber
          is deprecated and is replaced with fullAccountNumberList in include parameter and response.</li><br><li>profile
          is deprecated, and to retrieve the profile information, call the GET /verification/holderProfile API instead.</li>
      - name: providerAccountId
        value: ''
        type: query
        description: Comma separated providerAccountIds.
      - name: requestId
        value: ''
        type: query
        description: The unique identifier that returns contextual data
      - name: status
        value: ''
        type: query
        description: ACTIVE,INACTIVE,TO_BE_CLOSED,CLOSED
    docs: The get accounts service provides information about accounts added by the user.<br>By default, this service returns
      information for active and to be closed accounts.<br>If requestId is provided, the accounts that are updated in the
      context of the requestId will be provided in the response.<br>Pagination is made available to the advisors to retrieve
      account data of all users assigned to them. The skip and top parameters are used for pagination. In the skip and top
      parameters pass the number of re
  - info:
      name: Add Manual Account
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/accounts'
    docs: The add account service is used to add manual accounts.<br>The response of add account service includes the account
      name , account number and Yodlee generated account id.<br>All manual accounts added will be included as part of networth
      calculation by default.<br>Add manual account support is available for bank, card, investment, insurance and loan container
      only.<br><br><b>Note:</b><ul> <li>A real estate account addition is only supported for SYSTEM and MANUAL valuation type.</li></ul>
  - info:
      name: Migrate Accounts
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/accounts/migrateAccounts/:providerAccountId'
      params:
      - name: providerAccountId
        value: ''
        type: path
        description: providerAccountId
    docs: This service is associated with the open banking (OB) flow.<br>Before invoking this service, display all the associated
      accounts to the user by calling the GET /associatedAccounts API.<br>The migrate accounts API treats the user's consent
      acceptance to initiate account migration. Invoking this service indicates that the user has given the consent to access
      the associated account information from the financial institution.<br>If an existing provider supports bank, card, and
      loan accounts, and cho
  - info:
      name: Evaluate Address
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/accounts/evaluateAddress'
    docs: Use this service to validate the address before adding the real estate account.<br>If the address is valid, the
      service will return the complete address information.<br>The response will contain multiple addresses if the user-provided
      input matches with multiple entries in the vendor database.<br>In the case of multiple matches, the user can select
      the appropriate address from the list and then invoke the add account service with the complete address.<br><br><b>Note:</b>
      <ul><li>Yodlee recommend
  - info:
      name: Get Account Details
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/accounts/:accountId'
      params:
      - name: accountId
        value: ''
        type: path
        description: accountId
      - name: convertToCurrency
        value: ''
        type: query
        description: On-demand currency conversion parameter
      - name: include
        value: ''
        type: query
        description: profile, holder, fullAccountNumber, fullAccountNumberList, paymentProfile, autoRefresh<br><b>Note:</b>fullAccountNumber
          is deprecated and is replaced with fullAccountNumberList in include parameter and response.
    docs: The get account details service provides detailed information of an account.<br><br><b>Note:</b><li> fullAccountNumber
      is deprecated and is replaced with fullAccountNumberList in include parameter and response.</li>
  - info:
      name: Update Account
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/accounts/:accountId'
      params:
      - name: accountId
        value: ''
        type: path
        description: accountId
    docs: The update account service is used to update manual and aggregated accounts.<br>The HTTP response code is 204 (Success
      without content).<br>Update manual account support is available for bank, card, investment, insurance, loan, otherAssets,
      otherLiabilities and realEstate containers only.<br><br><b>Note:</b><li> A real estate account update is only supported
      for SYSTEM and MANUAL valuation type.</li> <li> A real estate account can be linked to a loan account by passing accountId
      of a loan accoun
  - info:
      name: Delete Account
      type: http
    http:
      method: DELETE
      url: '{{baseUrl}}/accounts/:accountId'
      params:
      - name: accountId
        value: ''
        type: path
        description: accountId
    docs: The delete account service allows an account to be deleted.<br>This service does not return a response. The HTTP
      response code is 204 (Success with no content).<br>
  - info:
      name: Get Historical Balances
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/accounts/historicalBalances'
      params:
      - name: accountId
        value: ''
        type: query
        description: accountId
      - name: fromDate
        value: ''
        type: query
        description: from date for balance retrieval (YYYY-MM-DD)
      - name: includeCF
        value: ''
        type: query
        description: Consider carry forward logic for missing balances
      - name: interval
        value: ''
        type: query
        description: D-daily, W-weekly or M-monthly
      - name: skip
        value: ''
        type: query
        description: skip (Min 0)
      - name: toDate
        value: ''
        type: query
        description: toDate for balance retrieval (YYYY-MM-DD)
      - name: top
        value: ''
        type: query
        description: top (Max 500)
    docs: The historical balances service is used to retrieve the historical balances for an account or a user.<br>Historical
      balances are daily (D), weekly (W), and monthly (M). <br>The interval input should be passed as D, W, and M to retrieve
      the desired historical balances. The default interval is daily (D). <br>When no account id is provided, historical balances
      of the accounts that are active, to be closed, and closed are provided in the response. <br>If the fromDate and toDate
      are not passed, the l
  - info:
      name: Get Latest Balances
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/accounts/latestBalances'
      params:
      - name: accountId
        value: ''
        type: query
        description: Comma separated accountIds.
      - name: providerAccountId
        value: ''
        type: query
        description: providerAccountId.
    docs: The latest balances service provides the latest account balance by initiating a new balance refresh request
- info:
    name: Verification
    type: folder
  items:
  - info:
      name: Get Verified Accounts
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/verification/verifiedAccounts'
      params:
      - name: accountId
        value: ''
        type: query
        description: Comma separated accountIds.
      - name: isSelected
        value: ''
        type: query
        description: Comma separated isSelected. Allowed values are true, false. <br>
      - name: providerAccountId
        value: ''
        type: query
        description: providerAccountId.
      - name: verificationStatus
        value: ''
        type: query
        description: Comma separated verificationStatus. Allowed values are SUCCESS, FAILED <br><b>Note:</b> If no value is
          passed, the implicit default value is SUCCESS.
    docs: The Verified Accounts API v1.1 provides information about the bank and investment accounts that the user  has selected
      for verification, during the Account Verification flow on FastLink 4. By default, the API only returns information of
      the accounts that were selected and have been successfully verified. <br><br>
  - info:
      name: Get Holder Profile
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/verification/holderProfile'
      params:
      - name: accountId
        value: ''
        type: query
        description: accountId
      - name: providerAccountId
        value: ''
        type: query
        description: providerAccountId.
    docs: The Holder Profile API service allows retrieving the user's profile details (i.e., PII data such as name, email,
      phone number, and address) that are available at the provider account and each account level. The API accepts the providerAccountId
      and retrieves the profile information available under it and all the details available under each of the associated
      accounts.  <br><br>This service can only be invoked by Yodlee API v1.1, FastLink 3, and FastLink 4 customers. <br><br>
  - info:
      name: Get Classification Summary
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/verification/classification/summary'
      params:
      - name: accountId
        value: ''
        type: query
        description: accountId
    docs: The get classification summary API service returns attributes that provide account-level and transaction-level summary
      for a user's account.<br><br>As a prerequisite, the Account Verification customers should have Transactions enabled
      to fetch a response. The API can be invoked only for an account verified by the user following the get verified accounts
      API call. If the prerequisite is not satisfied, an appropriate error will be returned on invoking the API.<br>
  - info:
      name: Get Verification Status
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/verification'
      params:
      - name: accountId
        value: ''
        type: query
        description: Comma separated accountId
      - name: providerAccountId
        value: ''
        type: query
        description: Comma separated providerAccountId
      - name: verificationType
        value: ''
        type: query
        description: verificationType
    docs: The get verification status service is used to retrieve the verification status of all accounts for which the MS
      or CDV process has been initiated.<br>For the MS process, the account details object returns the aggregated information
      of the verified accounts. For the CDV process, the account details object returns the user provided account information.<br>
  - info:
      name: Initiaite Challenge Deposit
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/verification'
    docs: The post verification service is used to initiate the matching service (MS) and the challenge deposit account verification
      (CDV) process to verify account ownership.<br>The MS and CDV process can verify ownership of only bank accounts (i.e.,
      checking and savings).<br>The MS verification can be initiated only for an already aggregated account or a providerAccount.<br>The
      prerequisite for the MS verification process is to request the ACCT_PROFILE dataset with the HOLDER_NAME attribute.<br>In
      the M
  - info:
      name: Verify Challenge Deposit
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/verification'
    docs: The put verification service is used to complete the challenge deposit verification (CDV) process.<br>This service
      is used only by the customer of CDV flow.<br>In the CDV process, the user-provided microtransaction details (i.e., credit
      and debit) is matched against the microtransactions posted by Yodlee. For a successful verification of the account's
      ownership both the microtransaction details should match.<br>The CDV process is currently supported only in the United
      States.<br><br><b>Notes:</b
- info:
    name: Cobrand
    type: folder
  items:
  - info:
      name: Cobrand Login
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/cobrand/login'
    docs: The cobrand login service authenticates a cobrand.<br>Cobrand session in the response includes the cobrand session
      token (cobSession) <br>which is used in subsequent API calls like registering or signing in the user. <br>The idle timeout
      for a cobrand session is 2 hours and the absolute timeout is 24 hours. This service can be <br>invoked to create a new
      cobrand session token. <br><b>Note:</b> This endpoint is deprecated for customers using the API Key-based authentication
      and is applicable only
  - info:
      name: Subscribe Event
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/cobrand/config/notifications/events/:eventName'
      params:
      - name: eventName
        value: ''
        type: path
        description: eventName
    docs: <b>Refer POST /configs/notifications/events/{eventName}.</b><br>The subscribe events service is used to subscribe
      to an event for receiving notifications.<br>The callback URL, where the notification will be posted should be provided
      to this service.<br>If the callback URL is invalid or inaccessible, the subscription will be unsuccessful, and an error
      will be thrown.<br>Customers can subscribe to REFRESH,DATA_UPDATES and AUTO_REFRESH_UPDATES event.<br><br><b>Notes</b>:<br>This
      service is not avai
  - info:
      name: Update Subscription
      type: http
    http:
      method: PUT
      url: '{{baseUrl}}/cobrand/config/notifications/events/:eventName'
      params:
      - name: eventName
        value: ''
        type: path
        description: eventName
    docs: <b>Refer PUT /configs/notifications/events/{eventName}.</b><br>The update events service is used to update the callback
      URL.<br>If the callback URL is invalid or inaccessible, the subscription will be unsuccessful, and an error will be
      thrown.<br><b>Note:</b> The content type has to be passed as application/json for the body parameter. <br>
  - info:
      name: Delete Subscription
      type: http
    http:
      method: DELETE
      url: '{{baseUrl}}/cobrand/config/notifications/events/:eventName'
      params:
      - name: eventName
        value: ''
        type: path
        description: eventName
    docs: <b>Refer DELETE /configs/notifications/events/{eventName}.</b><br>The delete events service is used to unsubscribe
      from an events service.<br>
  - info:
      name: Cobrand Logout
      type: http
    http:
      method: POST
      url: '{{baseUrl}}/cobrand/logout'
    docs: The cobrand logout service is used to log out the cobrand.<br>This service does not return a response. The HTTP
      response code is 204 (Success with no content).<br><b>Note:</b> This endpoint is deprecated for customers using the
      API Key-based authentication and is applicable only to customers who use the SAML-based authentication.<br>
  - info:
      name: Get Subscribed Events
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/cobrand/config/notifications/events'
      params:
      - name: eventName
        value: ''
        type: query
        description: eventName
    docs: <b>Refer GET /configs/notifications/events.</b><br>The get events service provides the list of events for which
      consumers subscribed <br>to receive notifications. <br>
  - info:
      name: Get Public Key
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/cobrand/publicKey'
    docs: <b>Refer GET /configs/publicKey.</b><br>The get public key service provides the customer the public key that should
      be used to encrypt the user credentials before sending it to Yodlee.<br>This endpoint is useful only for PKI enabled.<br>
- info:
    name: DataExtracts
    type: folder
  items:
  - info:
      name: Get userData
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/dataExtracts/userData'
      params:
      - name: fromDate
        value: ''
        type: query
        description: From DateTime (YYYY-MM-DDThh:mm:ssZ)
      - name: loginName
        value: ''
        type: query
        description: Login Name
      - name: toDate
        value: ''
        type: query
        description: To DateTime (YYYY-MM-DDThh:mm:ssZ)
    docs: The get user data service is used to get a user's modified data for a particular period of time for accounts, transactions,
      holdings, and provider account information.<br>The time difference between fromDate and toDate fields cannot be more
      than 60 minutes.<br>By default, pagination is available for the transaction entity in this API. In the first response,
      the API will retrieve 500 transactions along with other data. The response header will provide a link to retrieve the
      next set of transactio
  - info:
      name: Get Events
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/dataExtracts/events'
      params:
      - name: eventName
        value: ''
        type: query
        description: Event Name
      - name: fromDate
        value: ''
        type: query
        description: From DateTime (YYYY-MM-DDThh:mm:ssZ)
      - name: toDate
        value: ''
        type: query
        description: To DateTime (YYYY-MM-DDThh:mm:ssZ)
    docs: The get extracts events service is used to learn about occurrences of data extract related events. This service
      currently supports only the DATA_UPDATES event.<br>Passing the event name as DATA_UPDATES provides information about
      users for whom data has been modified in the system for the specified time range. To learn more, please refer to the
      <a href="https://developer.yodlee.com/resources/yodlee/data-extracts/docs/overview">Data Extracts</a> page.<br>You can
      retrieve data in increments of no m
- info:
    name: Providers
    type: folder
  items:
  - info:
      name: Get Providers
      type: http
    http:
      method: GET
      url: '{{baseUrl}}/providers'
      params:
      - name: capability
        value: ''
        type: query
        description: CHALLENGE_DEPOSIT_VERIFICATION - capability search is deprecated
      - name: dataset$filter
        value: ''
        type: query
        description: Expression to filter the providers by dataset(s) or dataset attribute(s). The defau

# --- truncated at 32 KB (74 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/yodlee/refs/heads/main/apis.yml