Getting API access to advisor CRMs

Updated Oct 17, 2026

Of the nine advisor CRMs we checked in October 2026, four publish API documentation openly (Wealthbox, Less Annoying CRM, HubSpot and Salesforce) and Practifi publishes a reference but gates calls behind an org or partner environment. For the other four, no public developer surface was found or the page could not be read.

This guide covers how a developer gets API access to the nine CRMs in our CRM category. Every statement comes from a record we saved on 2026-10-17 (checked October 2026), and the agents page explains what each state means. Where a fact isn’t on a public page, the guide says so. “Not found” does not mean the vendor has no API: a private one may exist behind a login or a customer agreement.

The CRMs side by side

Rate limits, webhooks and API descriptions differ a lot between the five that publish docs. They are covered one by one below.

CRMs that publish API docs

Wealthbox

Wealthbox’s developer site describes “REST-based resource URLs” that return JSON or XML. The record (checked October 2026) shows two ways in:

• Personal API access token. The account holder creates it in the Wealthbox settings page for API access tokens. The token goes in an ACCESS_TOKEN header. The docs limit what it is for: “Personal API access tokens are reserved for building personal integrations — such as those to in-house systems — and testing integration capabilities.”
• OAuth 2.0. The docs say it supports authorization code and refresh token grants, and that OAuth is required for integration partners who make an app available to mutual customers. Credentials are issued by email: you write to [email protected] with details about your application and ask for a client ID and client secret.

Limits: “one request/second over a five minute” sampling period, with short bursts allowed. Exceeding it returns HTTP 429.

What the docs don’t say: a sandbox or test environment, webhooks, SDKs, or an OpenAPI file. Examples use curl. Wealthbox also has a partnerships page and an integrations page that marks some integrations “via Zapier”. There is also an MCP connector, covered in the MCP guide.

Less Annoying CRM

The API is documented openly at its API docs. Facts from the record:

• Style. Every call is a POST to https://api.lessannoyingcrm.com/v2/ with a JSON body that names the function. We record this as RPC.
• Keys. The docs say to manage the account’s API keys on the Programmer API settings page, where you can enable or disable API access, view active keys and create new ones. They do not say which users can reach that page. The key goes alone in the Authorization header. An admin can turn API key access off for the account.
• OAuth. Only for registered integration partners, who “are registered with LACRM and given OAuth credentials.”
• Webhooks. Supported, for a limited set of CRM events. The page calls the system new.
• Integrations. The vendor’s integrations page says it connects to 5,000 more apps through Zapier.

The docs sections we read state no sandbox, rate limits, SDKs or OpenAPI file. The docs also describe the API as an advanced feature for capable programmers.

HubSpot

HubSpot is a general-purpose CRM that some advisors use. Its developer docs say nothing specific to wealth management.

• Getting access. Create a developer account at developers.hubspot.com, then build an app that uses OAuth or a static access token. The authentication overview says OAuth is required for multiple accounts, while static tokens are for installing in one account at a time.
• Sandbox. Developer test accounts are self-serve: click Create developer test account.
• Limits. Marketplace OAuth apps get 110 requests every 10 seconds per installing account (excluding the CRM Search API). Privately distributed apps get 100 per app per 10 seconds, plus a daily cap per account: 250,000 on Free and Starter, 625,000 on Professional (190 per app per 10 seconds), and 1,000,000 on Enterprise (190 per app).
• Also published. Webhooks, SDKs for Node, PHP, Python and Ruby, and OpenAPI specs listed in the docs index.
• MCP. HubSpot’s developer docs describe an MCP server for AI tools to reach HubSpot CRM data (see the Claude guide for the vendor’s wording). We hold no server record for it, so it has no page under /mcp.

The pages we captured don’t name an API style in words.

Salesforce Financial Services Cloud

The captured pages are general Salesforce platform docs, not Financial Services Cloud pages. The product page now calls it “Agentforce Financial Services (formerly Financial Services Cloud).”

• Getting access. You need a Salesforce org and a user with API access enabled. A free Developer Edition org is available for testing and development, which also makes the sandbox self-serve.
• Auth. The REST guide says a client application must use an external client app or a connected app and an OAuth 2.0 authorization flow. The captured pages don’t name the flow, so the record says OAuth 2.0 with the flow not named.
• Not found. Rate limits (the URL we guessed returned 404), webhooks, SDK list and an OpenAPI file link. We did not establish whether a Financial Services Cloud-specific MCP server exists, though Salesforce’s developer home links a post about exposing custom Apex as a hosted MCP tool.

Practifi

Practifi’s API reference is public and “sits atop the Salesforce Lightning Platform REST API.” Calling it is gated.

• Clients create a Connected App in Salesforce setup in their own Practifi org. They are pointed to a Salesforce partial copy sandbox through their Client Success team.
• Ecosystem partners email [email protected] for a development environment, which the page says it can create quickly. The page also describes SwaggerHub auto-mock URLs for development without an environment.
• Auth. OAuth 2.0 authorization code flow, with the authorization and token URLs on login.salesforce.com.
• Limits. The Salesforce platform cap per 24 hours, typically 15,000 plus 1,000 per user up to 1,000,000, shared across all of the org’s integrations.

Not found: webhooks, SDKs, a downloadable spec (the common spec paths returned 404 on 2026-10-17), and a public integrations list.

CRMs with nothing public to build against, or no readable page

Redtail CRM

The page that would hold the docs, redtailtechnology.com/api, returned HTTP 403 to automated reading, so the record is marked “couldn’t read automatically.” The readable pages describe a “flexible open API framework” and an integrations page, but contain no documentation or access instructions. That marketing sentence is the only basis for listing a native API. Redtail data is reachable another way: Orion’s connector for Claude reads and creates Redtail CRM records once a firm’s technical administrator enables it (see the MCP guide).

AdvisorEngine CRM, Advyzon and Salentica

• AdvisorEngine CRM. No developer or API page is linked from the home page, and /crm returned 404.
• Advyzon. Its home page describes one platform with built-in CRM. The integration paths we tried returned 404 and /api failed to load, so the record is marked “couldn’t read automatically” rather than “not found”.
• Salentica. salentica.com redirects to SS&C Black Diamond’s CRM page, which lists two CRM options built on the Salesforce Lightning Platform and Microsoft Dynamics 365. That page does not use the Salentica name, and no CRM developer docs were found. Black Diamond’s integrations page mentions a “Flexible API for Advanced Customization” for the Black Diamond platform, with no docs link.

Patterns in how access works

Two details matter when you plan a build:

• Single account versus many. HubSpot says static tokens install in one account at a time and OAuth is required for multiple accounts. Wealthbox and Less Annoying CRM tie OAuth to partner status. If your product serves many firms, the OAuth path is the one to check first.
• Limits are shared. Practifi’s cap is the org’s Salesforce limit, shared across every integration the org runs, so your calls compete with the firm’s other tools.

When a vendor has no public API

The records support a short list of options.

1. Ask the vendor. The Practifi and Wealthbox records show vendors that route some access through an email address. For the vendors with nothing published, we hold no contact on record, and an API may exist behind a login or a customer agreement.
2. Use an integration platform the vendor lists. Wealthbox’s integrations page marks some integrations “via Zapier,” and Less Annoying CRM says it connects to 5,000 more apps through Zapier. No record says AdvisorEngine CRM, Advyzon or Salentica do the same.
3. Go through another product’s connector. For Redtail, Orion’s Claude connector reaches Redtail CRM records through Orion’s gateway, and its tool names include creating notes and activities. A firm’s technical administrator enables it, not the developer.
4. Check the parent platform. Salentica’s page leads to SS&C Black Diamond and its Salesforce- and Dynamics-based CRM options. If a firm runs one of those, the platform’s own API applies. We did not capture Dynamics docs.
5. File exchange. The records for these nine CRMs do not describe file import or export, so we don’t claim it as an option for any of them.

Checking a record yourself

Each product page lists the quote and date behind every fact. If a vendor has published new docs since October 2026, email [email protected] with a public link and we will update the record. For the full set of products, see the products index. For AI-assistant connections to CRMs, see MCP servers in advisor technology and Connecting Claude to advisor tools.