Yodlee Core APIs

Name: Yodlee Core APIs
Brand: Yodlee Core APIs
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer Supportnone70 EndpointsREST

For Agents

Programmatically get transactions, cobrand login. Covers 70 operations.

Use for: I need to transactions, I want to cobrand login, Search for userdata, Find all providers

Install Jentic One Beta

Connect the Yodlee Core APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Yodlee Core APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Yodlee Core APIs.

Get Transactions

Cobrand Login

Subscribe Event

Update Subscription

GET STARTED

Start building with Yodlee Core APIs

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Yodlee Core APIs for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'get transactions', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

70 endpoints — this file describes the yodlee platform apis using the swagger notation.

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

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}

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Yodlee Core APIs none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get transactions') and Jentic returns the matching Yodlee Core APIs operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Yodlee Core APIs integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Yodlee Core APIs through Jentic.

What authentication does the Yodlee Core APIs use?

The Yodlee Core APIs uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Yodlee Core APIs

Connect the Yodlee Core APIs to your agent

Capabilities

Start building with Yodlee Core APIs

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs