canonical: https://jentic.com/apis/yodlee.com/yodlee # Yodlee Core APIs This file describes the Yodlee Platform APIs using the swagger notation. You can use this swagger file to generate client side SDKs to the Yodlee Platform APIs for many different programming languages. Yodlee supports the Java SDK and it is available here. You can generate a client SDK for Python, Java, JavaScript, PHP or other language. The API exposes 70 endpoints. ## For AI agents Programmatically get transactions, cobrand login. Covers 70 operations. ## Scope Does not handle payments, communications, or developer tools - use for crm only. ## Capabilities - Get Transactions - Cobrand Login - Subscribe Event - Update Subscription - Monitor Yodlee Core APIs operational status and events ## Use cases ### CRM Operations Use the Yodlee Core APIs to perform crm operations programmatically. The API provides 70 endpoints covering core functionality including get transactions, cobrand login, get userdata. Example prompt: Call GET /transactions to get transactions ### Automated Accounts Management Automate accounts operations by combining multiple Yodlee Core APIs endpoints. Agents can cobrand login and then get userdata in a single workflow. Example prompt: Call POST /cobrand/login to cobrand login, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Yodlee Core APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually. Example prompt: Search Jentic for 'get transactions', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /transactions | Get Transactions | | POST | /cobrand/login | Cobrand Login | | GET | /dataExtracts/userData | Get userData | | GET | /providers | Get Providers | | GET | /providers/{providerId} | Get Provider Details | | POST | /cobrand/config/notifications/events/{eventName} | Subscribe Event | | PUT | /cobrand/config/notifications/events/{eventName} | Update Subscription | | DELETE | /cobrand/config/notifications/events/{eventName} | Delete Subscription | ## Key resources - **Accounts** — Accounts API - **Auth** — Auth API - **Cobrand** — Cobrand API - **Configs** — Configs API - **DataExtracts** — DataExtracts API ## Why Jentic - **Setup:** Wiring Yodlee Core by hand means running its cobrand login to obtain a session, threading that session into each call, and handling retries yourself. Through Jentic you install once, import Yodlee Core from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Yodlee Core puts the provider id and notification event name in the URL path (/providers/{providerId}, /cobrand/config/notifications/events/{eventName}), so a rule can pin your agent to one provider or event: it reads that record and nothing else. You choose the operations it may call, so destructive ones like deleting a notification event are not included unless you add them. - **Credential handling:** Your Yodlee Core credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get transactions' or 'list providers', and Jentic returns the matching Yodlee Core operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Hubspot** — Alternative crm API - **Salesforce** — Alternative crm API - **Pipedrive** — Complementary crm API - **Zoho** — Complementary crm API ## FAQ ### What authentication does the Yodlee Core APIs use? The Yodlee Core APIs uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I get transactions with the Yodlee Core APIs? Yes. Use the GET /transactions endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Yodlee Core APIs? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I get transactions through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get transactions'. Jentic returns the matching Yodlee Core APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Yodlee Core APIs have? The Yodlee Core APIs exposes 70 endpoints covering accounts, auth, cobrand operations. ### Can I limit what my agent is allowed to do with the Yodlee Core API? Yes. Because you run Jentic One yourself, your own rules decide which Yodlee Core operations and credentials the agent may use. Since Yodlee Core puts the provider id and notification event name in the URL path (/providers/{providerId} and /cobrand/config/notifications/events/{eventName}), you can pin the agent to a single provider or event so it reads that record and nothing else. You also choose the operations it may call, so a destructive one like DELETE on a notification event is excluded unless you explicitly allow it.