Introduction

The MyCLM API is a REST API over HTTPS. It exposes the same features as the MyCLM app, with the same access rules: an integration sees and does exactly what its role allows, and everything it does is logged.

Who uses the API

You are	You use	Typical integration
A customer connecting your CRM, ERP or business software	An API key of your organization	Send a signature request when a deal is won, sync contacts, create follow-up tasks.
A software vendor embedding MyCLM in your product	A partner application	Create an organization per customer, provision users, act on behalf of each user (delegated OAuth).
A vendor connecting existing MyCLM customers	A partner application + OAuth consent	“Connect with MyCLM”: an administrator authorizes your app on their organization.

See Authentication for the details of each mechanism.

Base URL

Every path in this documentation is relative to the base URL of your environment. The code samples read it from the MLT_API_URL environment variable.

Environment	Base URL
Production	https://api.mylegitech.com Final production domain to be confirmed.
Local development	http://localhost:3100

export MLT_API_URL=http://localhost:3100

Conventions

• JSON everywhere. Requests and responses are UTF-8 JSON (Content-Type: application/json), except file uploads (multipart/form-data) and downloads (PDF, CSV).
• Identifiers are UUIDs (v7, roughly time-ordered). Treat them as opaque strings.
• Dates are ISO 8601 strings in UTC, e.g. 2026-10-01T09:30:00.000Z. Calendar dates (until of a recurrence) are YYYY-MM-DD.
• Partial updates use PATCH: omitted fields are unchanged, null clears a field.
• Lists return { "results": [...], "nextPageToken": "..." }. See Pagination.
• Errors return { "error": { "code", "message", "details" } } with a stable code. See Errors.
• Visibility. A resource you cannot see answers 404; a resource you can see but cannot change answers 403.

No SDK yet

There is no official client library yet: the API is plain HTTP and the samples use curl, Node.js fetch, Python requests and PHP Guzzle. The OpenAPI document lets you generate a client in any language.

Machine-readable specification

The full reference is published as an OpenAPI 3.1 document, served by the API itself at GET /openapi.json (public, no authentication) and bundled with this site at /openapi.json. Import it in Postman, Insomnia or your code generator.

QuickstartFrom zero to a signed document in a few minutes.

API referenceBrowse and try every endpoint.