Quickstart

1. Get a key

There is no public signup. Keys are issued from the partner dashboard once your application is approved. The raw value is shown once, at creation:

clmt_live_9f2aK4dQ8xR3mB1nT7cV

Store it before you leave the page. Manage keys from the partner dashboard at partner.clemta.com.

2. Call the API

Send the key as a bearer token. GET /me confirms who the key belongs to and which API version you are on:

curl https://api.clemta.com/v1/me \
  -H "Authorization: Bearer clmt_live_9f2aK4dQ8xR3mB1nT7cV"

Response

{
  "object": "me",
  "partner_id": "prt_0346sFPEvSkJvY8vt14NNw",
  "livemode": true,
  "key_last4": "T7cV",
  "api_version": "2026-08-13"
}

Use a clmt_test_ key to run against the sandbox instead. It creates nothing real.

3. Create a company

One call creates the account, the company, and the services on it. Use a test key first. Nothing real is created.

curl -X POST https://api.clemta.com/v1/companies \
  -H "Authorization: Bearer clmt_test_..." \
  -H "Idempotency-Key: 5f1c2a..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme", "ending": "llc", "state": "DE", "entity_type": "llc",
    "industry": "software",
    "account": {"first_name": "Ada", "last_name": "Lovelace", "email": "[email protected]"},
    "shareholders": [{"type": "individual", "first_name": "Ada", "last_name": "Lovelace",
                      "email": "[email protected]",
                      "relationship": {"title": "sole_owner", "percent_ownership": 100, "representative": true},
                      "tax_id_type": "ssn", "tax_id": "123-45-6789",
                      "address": {"country": "US", "line1": "1 Main St", "city": "Dover", "state": "DE", "postal_code": "19901"}}],
    "services": ["ein"]
  }'

The company comes back in requires_information: each individual owner still owes an identity document (document.status is required). Attach one inline with passport (a file id from POST /v1/files), or hand your client a hosted upload page - POST /v1/companies/{id}/verification-sessions returns a url you forward, no key needed. Once every owner’s document is received, the company moves on.

4. Follow along

curl "https://api.clemta.com/v1/events?limit=10" -H "Authorization: Bearer clmt_test_..."

In the sandbox, drive the lifecycle yourself:

curl -X POST https://api.clemta.com/v1/sandbox/companies/cmp_.../simulate \
  -H "Authorization: Bearer clmt_test_..." \
  -d '{"event": "company.status.changed", "status": "active"}'

Moving a test company to active fires company.status.changed and company.incorporated, exactly as the real transition would. Many of the catalog’s events are simulable this way (company.ein.assigned, service_order.completed, tax_filing.*, file.created, invoice.finalized…). See Modes and the sandbox.

5. Next

How it fits together: the objects and the lifecycle.
Requirements: everything Clemta asks of you, and how your client answers.
Webhooks: ordered, signed delivery of every event.

Get Started

The platform

Building on the API

Versioning

1. Get a key

2. Call the API

3. Create a company

4. Follow along

5. Next

​1. Get a key

​2. Call the API

​3. Create a company

​4. Follow along

​5. Next

1. Get a key

2. Call the API

3. Create a company

4. Follow along

5. Next