domain: yodlee.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain your Yodlee API credentials (clientId and secret) from the Envestnet Yodlee developer portal and generate a JWT access token for your application by calling the token endpoint with your credentials.
Create or retrieve a Yodlee user (cobrand user) for each end user in your system by calling the user registration or login endpoint; obtain a user-level access token.
Initialise FastLink by passing the user access token and your configuration parameters (flow type: add, edit, refresh; optional providerAccountId for existing accounts) to the FastLink JavaScript embed or mobile SDK.
Handle the FastLink postMessage or callback events in your host page to detect successful account addition (onSuccess), errors (onError), and exit events; extract the providerAccountId from the success callback.
Retrieve linked account details and transactions using the Yodlee Data API with the user's access token: GET /accounts for account list and GET /transactions for transaction history, using date range and account filters.
Implement periodic refresh by calling the account refresh endpoint or relying on Yodlee's automatic background refresh; poll account status to know when fresh data is available.
Known gotchas
FastLink is a hosted widget — Yodlee manages the institution connection credentials, meaning you never see the user's bank username/password, but it also means you have limited control over the UI and connection error messaging.
Yodlee uses a cobrand and cobrand user model for multi-tenancy; ensure each end user has their own cobrand user context so that their linked accounts are isolated and not visible across users.
Transaction data from Yodlee is categorised and enriched automatically, but category mappings and merchant name normalisation may differ from your expected values; do not hard-code against specific Yodlee category IDs without mapping them explicitly in your code.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?