Skip to main content
The Partner API lets you offer company formation and services under your own brand, and track every order programmatically.

Base URL

Test-mode keys (clmt_test_) run against a sandbox that creates nothing real. Live-mode keys (clmt_live_) run against real companies and billing.

Where to start

Authentication

Bearer keys, environments, and the error shape.

Quickstart

Your first authenticated call in a minute.

Partner dashboard

Keys, webhooks, logs, billing, branding: the map of partner.clemta.com.

Filtering and expanding

Filters, cursor pagination, and expansions on list endpoints.

Idempotency

Retry writes safely with an idempotency key.

Build with an AI agent

Skills and a docs search server for Claude Code, Cursor, and the rest.

OpenAPI specs

Download the description, per version, and generate a client.

Understand the platform

How it fits together

The objects, the modes, and the one rule behind every design choice.

Company lifecycle

Statuses, stages, identity documents, and the events at each step.

Requirements

Documents, forms, and the asks your customer answers without a key.

Service orders

Ordering, fulfilment steps, recurring services, the form standard.

Billing

Partner prices, a charge per order, one invoice a month.

Files

Reading deliverables back, proxied through the API.

Whitelabel

Your customer never hears from Clemta. What you receive instead.

Webhooks

Every event, delivered and signed per Standard Webhooks.

Conventions

  • Responses are JSON. Errors follow a single envelope with a machine-readable code. See Errors.
  • Limits are published on every response. See Rate Limiting.
  • Every object names its own type in an object field, so it stays identifiable when nested or delivered in an event.
  • Support is [email protected]. Include the request_id from the response when you write about a specific call.
Last modified on October 20, 2026