New report2026 State of AI at Enterprise RIAs2026 State of AI at RIAsRead it freeOn demandOther eventsNext: AI for Mid-Sized Law, Nov 5
eMoney APIIntegration guide

Integrate the eMoney API.Caddi writes and runs the integration for you.

eMoney has a REST API. You sign up on eMoney's developer portal, then contact eMoney for access to a paid API package. Authentication is certificate-based: an X.509 certificate from a trusted authority, exchanged for tokens.

  • 99%of agent runs complete successfully
  • ~45 minon average to build your first agent
  • 1M+back-office tasks completed
01Getting access

The connection is a project before it does anything.

Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. 60 concurrent calls, and 250 calls per hour on the Monte Carlo endpoints.

On your own

Register an app, store eMoney credentials, refresh tokens and code around the rate limits.

With Caddi

Connect your eMoney account once. Caddi holds the connection.

02The whole job

The job doesn't stop at eMoney.

An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The eMoney API only reaches eMoney.

On your own

Each extra system is another API, another set of credentials, another integration to own.

With Caddi

One automation runs across every tool the job touches, each through its API.

03After launch

Someone has to own the code.

API versions change, fields get added and your process moves.

On your own

A developer patches and redeploys the integration each time.

With Caddi

The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.

What the eMoney API gives you

Type
REST (JSON)
Authentication
X.509 certificate + OAuth 2.0
Who can get access
You sign up on eMoney's developer portal, then contact eMoney for access to a paid API package. Authentication is certificate-based: an X.509 certificate from a trusted authority, exchanged for tokens.
What it covers
Clients, people, tasks and alerts, assets, liabilities, income, expenses, insurance and planning data, Vault files, and premium projections such as cash flow and Monte Carlo.
Limits
60 concurrent calls, and 250 calls per hour on the Monte Carlo endpoints.

Official docs: developer.emoneyadvisor.com. Checked September 2026. Vendors change access terms, so confirm with eMoney before you build.

When to build the eMoney integration in-house

When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting eMoney work off someone's desk, the build is the slow part, and Caddi does it for you.

What teams usually want the eMoney API for

  • Annual review prep packet

    Caddi gathers updated client facts from the CRM and custodian, refreshes eMoney inputs, generates the review packet, and files it for the advisor.

  • Client fact-update sync

    When a client returns an updated fact form, Caddi parses it, updates eMoney and the CRM, and routes any new beneficiary or address change for compliance review.

  • Deliverable archiving

    Caddi watches for newly generated plan PDFs, applies the firm's metadata, files them in the household record, and updates the related CRM task.

Everything Caddi does with eMoney.

eMoney API questions

Does eMoney have an API?

Yes. eMoney has a REST API, authenticated with X.509 certificate + OAuth 2.0. The official documentation is at https://developer.emoneyadvisor.com/.

How do I get access to the eMoney API?

You sign up on eMoney's developer portal, then contact eMoney for access to a paid API package. Authentication is certificate-based: an X.509 certificate from a trusted authority, exchanged for tokens.

Does the eMoney API have rate limits?

60 concurrent calls, and 250 calls per hour on the Monte Carlo endpoints.

Can I connect eMoney to my other tools without writing code against its API?

Yes. With Caddi you show the eMoney task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across eMoney and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.

Do I need a developer to automate eMoney with Caddi?

No. There is no integration code for you to write or maintain. Every automation Caddi builds for eMoney is reviewed before it runs in production, and every run is logged.