Skip to main content
Assistable Direct is Assistable with its own native CRM. A Direct sub-account stores its contacts, conversations and messages in Assistable itself — there’s no GoHighLevel (or any external CRM) in the loop. You provision accounts, add users, fund wallets and talk to assistants entirely over the API. Direct runs on the same /v3 endpoints as the rest of the platform, so everything you already know about the v3 API applies — the auth model, the response envelope, rate limits and the interactive reference. This section collects the pieces that are specific to Direct.

​
How it fits together

1

Provision a Direct sub-account

POST /v3/subaccounts creates a native sub-account and returns a webhook URL + secret. See Provisioning.
2

Add users

Invite people to the sub-account with POST /v3/subaccounts/{id}/users — passwords are stored bcrypt-hashed, never in plain text.
3

Fund the wallet

Credit the wallet so the account can run chat and voice. See Wallets.
4

Send messages in

Forward inbound messages to the Direct listener; Assistable auto-creates the contact + conversation and replies with the bound assistant. See Webhook ingestion.
5

Use the rest of v3

Assistants, contacts, conversations, chat, knowledge, tools, calls, numbers, alerts and monitor-rules all work against a Direct sub-account exactly as they do elsewhere — scoped by X-Subaccount-Id. Browse them in the API Reference tab.

​
What’s different on Direct

  • Native CRM — contacts, conversations and messages live in Assistable, not GHL.
  • Provisioning API — create sub-accounts, users and wallets programmatically (the Subaccounts resource).
  • Authenticated inbound webhook — one signed endpoint ingests messages and triggers an AI reply.
Appointments are not yet available on Direct — that resource is still GoHighLevel-scoped. Everything else in v3 works on a Direct sub-account.