canonical: https://jentic.com/apis/addepar.com/addepar # Addepar API 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. ## For AI 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. ## Scope Does not place trades, move money, or generate client tax forms - use for portfolio reporting, entity management, and document storage only. ## Capabilities - 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 - List positions and transactions to drive reconciliation and reporting workflows - Upload, list, and retrieve files attached to entities for client document workflows - Bulk-edit entities via PATCH on the /entities collection for efficient mass updates ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Entities** — Clients, households, and accounts - the core hierarchy supporting create, get, edit, and delete operations including bulk variants. - **Portfolio** — Query endpoint returning performance, exposure, and allocation metrics across entities. - **Users** — Firm user records with create, list, and update operations for access management. - **Groups** — Permission groups that users are assigned to for access control. - **Positions** — Holdings within accounts at a point in time. - **Transactions** — Trade and cash-flow records on accounts. - **Files** — Documents attached to entities for client paperwork workflows. ## Why Jentic - **Setup:** Wiring the Addepar API by hand means combining its firm-scoped Addepar-Firm header with HTTP Basic credentials and threading entity ids through reporting and entity endpoints without a published spec. Through Jentic you install once, import the Addepar API from the API Directory, store the firm key and Basic credentials once, and your agent calls it. - **Permission scoping:** Addepar puts the entity id in the URL path (/entities/{id}), so a rule can pin your agent to one entity: it can read and patch that entity and nothing else. You choose the operations it may call, so creating entities or users is not included unless you add it. - **Credential handling:** 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. - **Discovery method:** 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. ## Related APIs - **Envestnet API** — Wealth-management platform covering managed accounts, performance, and reporting. - **Refinitiv API** — Market data provider supplying prices and reference data into wealth platforms. - **Salesforce REST API** — CRM that holds client relationship data; pairs with Addepar's portfolio data. ## FAQ ### 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.