Wealthbox API Access Tokens

Wealthbox service account credentials let your workflows authenticate to Wealthbox with a pasted API access token instead of a personal OAuth connection. Wealthbox doesn't document an expiry for these tokens — treat them as long-lived until you revoke them — so workflows keep running without anyone renewing an OAuth consent.

Prerequisites

Wealthbox trial accounts cannot use the API (calls return 402 Trial expired). If you don't see an API Access section in your Wealthbox settings, contact Wealthbox support before continuing.

Wealthbox tokens are tied to the user who creates them and carry that user's permissions. For production workflows, create the token from a dedicated service login with adequate record visibility rather than a personal account — the credential then survives any individual employee leaving.

Creating the API Access Token

Log in to Wealthbox, open Settings (the three-dot menu), and go to API Access (direct link: app.crmworkspace.com/settings/access_tokens)

Click Create Access Token, give it a label (e.g. sim-workflows), and save

Copy the token. Wealthbox doesn't document an expiry for API access tokens; you can revoke it from this same page at any time.

The token carries the full permissions of the user who created it — there is no scope selection. Treat it like a password: do not commit it to source control or share it publicly. Sim encrypts the token at rest.

Adding the Service Account to Sim

Open your workspace Settings and go to the Integrations tab

Search for "Wealthbox Service Account" and click it, then click Add to Sim and choose Add access token

Paste the API access token, and optionally set a display name and description

Click Add access token. Sim verifies the token by calling Wealthbox's /v1/me endpoint — if it fails, you'll see a specific error explaining what went wrong.

The token is encrypted before being stored.

Using the Service Account in Workflows

Add a Wealthbox block to your workflow. In the credential dropdown, your Wealthbox service account appears alongside any OAuth credentials. Select it and configure the block as you normally would.

The block calls Wealthbox's API (api.crmworkspace.com) with the token. The credential acts as the Wealthbox user who created the token — contacts, tasks, and notes the workflows touch are the ones that user can see under Wealthbox's permission settings.

Common Questions

API access tokens are long-lived and don't require any user to sit through a consent flow — they stay valid until you revoke them, which is what you want for an automated workflow. OAuth connections are tied to one person's session.

No — a token carries the full permissions of the user who created it. Authorization in Wealthbox is scoped to individual users, not organizations. If a workflow gets a 403 on a specific record, the token's user lacks visibility to that record — adjust the user's permissions in Wealthbox.

Trial accounts are blocked from the Wealthbox API, and some accounts may not show the section. Contact Wealthbox support if API Access is missing from your Settings.

Wealthbox doesn't document an expiry for API access tokens — expect them to work until revoked from the API Access settings page. If a workflow suddenly fails with a 401, the most likely cause is that someone revoked the token.

Wealthbox doesn't document workspace selection for API tokens. The API reports the token user's current workspace in /v1/me (current_user.account) — if your data spans multiple workspaces, test which workspace the token reads before relying on it.

There's no rotation API — create a new token from the API Access settings page, update the credential in Sim with the new token, and once it's working, revoke the old one.