Subaccounts

A subaccount is a separate account under yours for one of your clients. Agencies, call centers and platforms create one per client.

What each subaccount has

• Its own numbers, caller ID pools and number reputation. A spam label on one client's number never affects another client.
• Its own do-not-call list, consent records and compliance settings.
• Its own recordings, transcripts and retention rules.
• Its own API keys and webhook endpoints.
• A billing view with its own usage and call records.
• Its own National Do Not Call Registry subscription. A subscription cannot be shared across clients.
• Its own SMS brand registration and WhatsApp account.

Agents, lead lists and dial sessions belong to one subaccount. Calls placed in a subaccount use its numbers, caller name and registrations.

Create a subaccount

Each subaccount is reviewed as its own business before it can call or text. We verify the client's legal name, registration, tax ID, address, website and owners, and check them against US sanctions lists. A subaccount starts in in_review with every capability pending. No capability turns on, inbound included, until your client accepts the subaccount terms and signs its compliance certification. After that each feature turns on when its checks pass: inbound numbers first, then outbound calling, texting and recording.

What we need from each client depends on how they call:

• Every client: legal name, EIN, address, website, a representative, owners with 25% or more, what they sell and who they call.
• Sales calls to consumers: the client's own National Do Not Call Registry subscription, their do-not-call policy, call scripts, how they collect consent and where their leads come from.
• Calls into states that require telemarketer registration: the registration number or the exemption the client relies on.
• Texting: a brand and campaign registration in the client's business name.
• Some industries need more. Collections, Medicare and health care, lending and solar are reviewed by hand. Some industries are not accepted. See the acceptable use policy.

You can send these fields with the API and upload documents, or send your client the setup link from onboarding_url. Your client signs our terms and their compliance statement themselves.

Setup is $1,000 one time, per subaccount. There is no monthly fee per subaccount.

POST/v1/accounts

curl https://api.liveleg.dev/v1/accounts \
  -H "Authorization: Bearer $LIVELEG_API_KEY" \
  -H "Idempotency-Key: client-hollis-dental" \
  -d name="Hollis Family Dental" \
  -d legal_name="Hollis Family Dental PLLC" \
  -d ein=00-0000000 \
  -d contact_email=ops@hollisdental.example

const res = await fetch('https://api.liveleg.dev/v1/accounts', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.LIVELEG_API_KEY}`,
    'Content-Type': 'application/json',
    'Idempotency-Key': 'client-hollis-dental',
  },
  body: JSON.stringify({
    name: 'Hollis Family Dental',
    legal_name: 'Hollis Family Dental PLLC',
    ein: '00-0000000',
    contact_email: 'ops@hollisdental.example',
  }),
});
const account = await res.json();

import os, requests

account = requests.post(
    "https://api.liveleg.dev/v1/accounts",
    headers={
        "Authorization": f"Bearer {os.environ['LIVELEG_API_KEY']}",
        "Idempotency-Key": "client-hollis-dental",
    },
    json={
        "name": "Hollis Family Dental",
        "legal_name": "Hollis Family Dental PLLC",
        "ein": "00-0000000",
        "contact_email": "ops@hollisdental.example",
    },
).json()

{
  "id": "acc_hollis_dental",
  "object": "account",
  "name": "Hollis Family Dental",
  "parent_id": "acc_ridgeline",
  "status": "in_review",
  "capabilities": { "inbound": "pending", "outbound_consumer": "pending", "sms": "pending", "recording": "pending" },
  "requirements": {
    "currently_due": ["attestations.subaccount_terms", "attestations.seller_compliance", "documents.ein_letter", "documents.consent_form", "documents.script"],
    "pending_verification": ["owners[0].screening"]
  },
  "onboarding_url": "https://liveleg.dev/onboard/acc_hollis_dental?t=...",
  "livemode": true,
  "created_at": "2026-11-02T17:20:41Z"
}

Requirements and documents

GET /v1/accounts/{id}/requirements lists what is still due for each feature. Upload documents with POST /v1/accounts/{id}/documents. account.requirements_updated and account.capability_updated tell you when something changes. We ask again for some items each year, and when a registration or subscription expires.

POST/v1/accounts/{id}/documents

curl https://api.liveleg.dev/v1/accounts/acc_hollis_dental/documents \
  -H "Authorization: Bearer $LIVELEG_API_KEY" \
  -F type=dnc_subscription \
  -F file=@dnc-subscription.pdf

Keys and acting as a subaccount

A subaccount key works only inside that subaccount. Give it to a client or to a service that runs for one client. Your parent key can act on any subaccount by adding the Liveleg-Account header to a request. Without the header, the request runs on the parent account.

curl "https://api.liveleg.dev/v1/call_records?limit=20" \
  -H "Authorization: Bearer $LIVELEG_API_KEY" \
  -H "Liveleg-Account: acc_hollis_dental"

const res = await fetch('https://api.liveleg.dev/v1/call_records?limit=20', {
  headers: {
    Authorization: `Bearer ${process.env.LIVELEG_API_KEY}`,
    'Liveleg-Account': 'acc_hollis_dental',
  },
});
const records = await res.json();

import os, requests

records = requests.get(
    "https://api.liveleg.dev/v1/call_records",
    headers={
        "Authorization": f"Bearer {os.environ['LIVELEG_API_KEY']}",
        "Liveleg-Account": "acc_hollis_dental",
    },
    params={"limit": 20},
).json()

Every event carries account_id. One endpoint on the parent can receive the events for all subaccounts.

Usage and billing

Usage is reported per subaccount with the same line items as the invoice. Billing works one of two ways:

• One bill. The parent account gets one invoice for itself and all subaccounts.
• Per subaccount. Each subaccount gets its own invoice.

The minimum spend applies to the parent account. Platforms that resell calling to their own customers can read more on Liveleg for platforms.

curl "https://api.liveleg.dev/v1/usage?account_id=acc_hollis_dental&from=2026-10-01&to=2026-10-31" \
  -H "Authorization: Bearer $LIVELEG_API_KEY"