Envestnet API

Name: Envestnet API API
Brand: Envestnet API
Availability: InStock

✓ Official Vendor SpecFinanceBankingbearer, apiKey24 EndpointsREST

For Agents

Aggregate bank, brokerage, and credit accounts, retrieve categorised transactions, and read holdings and statements through the Envestnet Yodlee platform.

Quickstart

Get started with Envestnet API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list a user's transactions"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Envestnet API API.

Read, update, or delete the authenticated user via /user

List a user's aggregated accounts and update or remove individual account links

Retrieve categorised transactions and the available transaction categories

GET STARTED

Start building with Envestnet API API

Explore with Jentic

View OpenAPI Document

Use for: Register a new end user with the Envestnet platform, List all linked accounts for the authenticated user, Retrieve transactions for an account in the last 90 days, Get the count of transactions matching specific filters

Not supported: Does not handle payment initiation, lending decisions, or trade execution — use for account aggregation, transaction retrieval, holdings, and statements only.

Envestnet, through its Yodlee aggregation platform, provides account aggregation, transaction enrichment, and wealth-management data APIs used by financial advisors, fintechs, and large institutions. The published surface covers user registration, account aggregation, transaction retrieval and categorisation, provider browsing, holdings, and statements. With 24 endpoints, it forms a working base for personal financial management, advisor dashboards, and account-based onboarding flows where the customer needs to link external bank, brokerage, or credit accounts.

Use Cases

Patterns agents use Envestnet API API for, with concrete tasks.

★ Personal Financial Management Dashboard

Build a PFM app that lets users link external bank, credit card, and brokerage accounts via /providerAccounts, then displays categorised transactions retrieved from /transactions. The category list from /transactions/categories powers spending breakdowns and budgets. A typical PFM build uses these endpoints as the backbone for the data layer.

Call GET /transactions for the user with date range last 90 days and group results by the category field for a spending view.

Advisor Holdings View

Wealth advisors use the holdings endpoint to consolidate a client's brokerage positions across linked institutions, then surface them alongside performance data in an advisor dashboard. Statements retrieved from the API support compliance and reporting workflows. Pairs naturally with portfolio analytics tooling.

Read holdings for the authenticated user and group by accountId to show consolidated positions across linked brokerage accounts.

Account Onboarding and Linking

Onboard a new end user with POST /user/register, then walk them through linking a financial institution by browsing GET /providers and creating a provider account via the providerAccounts flow. The integration handles refresh state and errors so the consumer experience is consistent across thousands of supported institutions.

Submit POST /user/register for a new end user, then list providers via GET /providers to surface the institution picker.

AI Agent Financial Assistant Through Jentic

An AI financial assistant uses Jentic to discover Envestnet operations by intent and answers user questions like 'how much did I spend on groceries last month?' by chaining account list, transaction retrieval, and category data. The Envestnet bearer and cobrand credentials stay in the Jentic vault and never enter the agent's prompt context.

Search Jentic for 'list user transactions', load GET /transactions, and execute it for the linked user with date range last 30 days.

Key Endpoints

24 endpoints — envestnet, through its yodlee aggregation platform, provides account aggregation, transaction enrichment, and wealth-management data apis used by financial advisors, fintechs, and large institutions.

METHOD

PATH

DESCRIPTION

POST

/user/register

GET

/user

Read the authenticated user

GET

/accounts

List the user's aggregated accounts

GET

/transactions

Retrieve transactions for the user

GET

/transactions/categories

List available transaction categories

PUT

/transactions/{transactionId}

Update a transaction (e.g. recategorise)

GET

/providers

Browse supported financial providers

GET

/providerAccounts

List provider account links and refresh state

POST

/user/register

GET

/user

Read the authenticated user

GET

/accounts

List the user's aggregated accounts

GET

/transactions

Retrieve transactions for the user

GET

/transactions/categories

List available transaction categories

Why though Jentic?

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

Credential isolation

Envestnet bearer tokens and the cobrand Api-Version key are stored encrypted in the Jentic vault (MAXsystem). Agents call /accounts, /transactions, and /providers through scoped tokens — neither credential ever enters the agent's prompt context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list a user's transactions') and receive the matching Envestnet operation with its input schema, so the agent calls GET /transactions without scraping vendor docs.

Time to first call

Direct Envestnet integration: 3-5 days to wire up the dual-credential auth, provider linking flow, transaction pagination, and error handling. Through Jentic: about an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Plaid

Account aggregation and open banking API with strong U.S. and EU coverage

Choose Plaid when consumer fintech onboarding is the priority. Use Envestnet when wealth-management features such as holdings and advisor workflows are part of the product.

Alternative

Aggregation and data enrichment API focused on financial institutions

Pick MX for U.S. banks and credit unions wanting deep enrichment. Stick with Envestnet for advisor and Yodlee-backed aggregation flows.

Complementary

Xero Accounting

Push categorised transactions into a small-business accounting ledger

Use Xero after Envestnet aggregation for SMB-facing flows that need accounting reconciliation in addition to PFM.

FAQs

Specific to using Envestnet API API through Jentic.

What authentication does the Envestnet API use?

The Envestnet API uses HTTP bearer tokens for the user-bound session and a cobrand API key passed in the Api-Version header. Both credentials must be present on each request. Through Jentic, both are stored encrypted in the vault (MAXsystem) and never enter the agent context.

Can I aggregate bank accounts with the Envestnet API?

Yes. The /providers and /providerAccounts endpoints support linking and managing aggregated bank, credit, and brokerage accounts via the Yodlee aggregation backbone. /accounts then exposes the resulting account records for the user.

How do I retrieve categorised transactions?

Call GET /transactions with the desired filters; each transaction includes a category field. GET /transactions/categories returns the available category taxonomy if you need it for filtering or display, and PUT /transactions/{transactionId} lets you recategorise a transaction.

What are the rate limits for the Envestnet API?

The OpenAPI spec does not publish numeric rate limits. Envestnet applies plan-based limits at the cobrand level and across data partner endpoints — contact your Envestnet account manager for the limits attached to your environment.

How do I list a user's accounts through Jentic?

Search Jentic for 'list aggregated accounts for a user', load GET /accounts, and execute it with the user's bearer token. Get started at https://app.jentic.com/sign-up.

Does the Envestnet API support holdings and statements?

Yes. The Holdings, Derived Data, and Statements tags expose endpoints used by advisor and wealth-management apps to consolidate brokerage positions and pull statements alongside the standard banking transaction surface.