Addepar API

Name: Addepar API
Brand: Addepar API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey, basic51 EndpointsREST

For Agents

Query Addepar portfolio data, manage entities and users, and run portfolio queries across clients and accounts. Used by wealth-management agents to surface holdings, transactions, and performance figures.

Install Jentic One Beta

Connect the Addepar API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Addepar API, 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 Addepar API.

Manage Addepar entities - clients, households, legal entities, and accounts - through create, edit, and delete operations

Run portfolio queries that return performance, exposure, and allocation metrics across selected entities and date ranges

Read and update users and assign them to permission groups for access control

GET STARTED

Start building with Addepar API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Addepar API, keeping it validated and agent-ready. Addepar is a wealth management technology platform used by RIAs, family offices, and large advisory firms to track multi-asset-class portfolios. The API exposes entities (clients, accounts, holdings), portfolio query endpoints for performance and exposure analysis, users and groups for permissions, and files for document storage. Authentication combines an Addepar-Firm header (API key) with HTTP Basic credentials, scoping each call to a specific firm tenant.

Use Cases

Patterns agents use Addepar API for, with concrete tasks.

★ Advisor portfolio review

Wealth advisors prepare for client meetings by pulling holdings, performance, and allocation figures across the household. The /portfolio/query endpoint returns those figures in a single call when given a list of entity IDs and a date range, removing the need to navigate the Addepar UI per client. The same query can be parameterised across the advisor's full book to drive a daily review email.

POST /portfolio/query with entity_ids for a household, period 'YTD', and metrics ['return', 'allocation_by_asset_class'] and return the results.

Client onboarding automation

Operations teams onboard new clients by creating an entity tree (household > individuals > accounts) in Addepar so portfolio data can flow in. Combining POST /entities with subsequent linkage calls, an automation can replicate a CRM record into Addepar in seconds, ensuring data captured at signup is reflected on the advisor dashboard the next day.

Call POST /entities to create a household, then POST /entities again for each member individual and their accounts, linking them via the parent fields.

User access management for compliance

Compliance officers need to review and adjust which advisors can see which clients. The Addepar users and groups endpoints make this auditable and scriptable: list all users, list groups, and PATCH user-group memberships to enforce role boundaries. This replaces ticket-driven manual adjustments in the Addepar admin UI.

GET /users to list all firm users, then PATCH the target user's groups to add 'Compliance Read-Only'.

AI agent client briefing via Jentic

An AI agent for a wealth advisor uses Jentic to call the portfolio query endpoint when the advisor asks 'how is the Smith household performing this year'. Jentic returns the operation schema, the agent fills entity_ids and a date range, and the response is summarised in plain English. The Addepar firm key and basic credentials never enter the agent's context - Jentic injects them at execute time.

Use Jentic to search 'addepar portfolio query', load the POST /portfolio/query schema, and execute with the Smith household entity_id and YTD period.

Key Endpoints

51 endpoints — jentic publishes the only available openapi specification for addepar api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/entities

Get all entities

POST

/entities

Create an entity

PATCH

/entities/{id}

Edit an entity

POST

/portfolio/query

Query portfolio data

GET

/users

Get all users

POST

/users

Create a user

GET

/entities

Get all entities

POST

/entities

Create an entity

PATCH

/entities/{id}

Edit an entity

POST

/portfolio/query

Query portfolio data

GET

/users

Get all users

POST

/users

Create a user

Why Jentic?

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

Credential isolation

Your Addepar firm API key and HTTP Basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'query household portfolio performance', and Jentic returns the matching Addepar operation with its input schema so the agent calls the right endpoint without browsing the reference docs, which matters because Addepar does not publish a public OpenAPI spec.

Time to first call

FAQs

Specific to using Addepar API through Jentic.

Why is there no official OpenAPI spec for Addepar API?

Addepar does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Addepar API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Addepar API use?

Addepar combines two schemes: an Addepar-Firm header carrying the firm-scoped API key, and HTTP Basic credentials for the calling user. Jentic stores both in your Jentic One instance and attaches them at execute time so neither the firm key nor the basic credentials appear in agent context.

Can I run portfolio performance queries with the Addepar API?

Yes. POST /portfolio/query accepts a list of entity IDs, a date range, and a set of metrics (returns, allocation, exposure) and returns the computed values in one response. This is the same engine that powers the Addepar UI's analytics views.

How do I create a new client entity through Jentic?

Search Jentic for 'create entity in addepar', load the POST /entities schema, and execute with the entity payload (type 'household' or 'individual', name, and parent links). Jentic returns the new entity ID, which can then be used to attach accounts.

Are there rate limits on the Addepar API?

Addepar enforces per-firm rate limits that vary by contract; the spec does not declare a fixed value. When 429 responses are returned, Jentic surfaces them unchanged so retry logic can read the Retry-After header.

Does this API execute trades or move money?

No. Addepar is a reporting and analytics platform - the API reads positions and transactions but does not place orders or initiate transfers. Trade execution requires a separate brokerage or custodian integration.

Can I limit what my agent is allowed to do with the Addepar API?

Yes. Because you run Jentic One yourself, your own rules decide which Addepar operations and credentials the agent may use. Since Addepar puts the entity id in the URL path (/entities/{id}), you can pin the agent to a single entity so it only reads and patches that one entity and nothing else. You also pick the exact operations it may call, so higher-risk actions like creating new entities or adding users are excluded unless you explicitly allow them.

Addepar API

Connect the Addepar API to your agent

Capabilities

Start building with Addepar API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs