ContractGen

API reference

The ContractGen HTTP API.

Twenty endpoints. One spec. Everything below is generated from the Rust source — when the spec disagrees with the running service, the spec is wrong. Most calls require an Authorization: Bearer <tenant-key> header. The signing and status endpoints use opaque per-party tokens instead; both are documented inline.

How authentication works.

Three credentials, three purposes.

Tenant API key
Issued to integrating applications; used for /v1/envelopes/* endpoints.
Signing token
Delivered only via email to the signer; used for /sign/{token}/* endpoints. Never returned in any API response.
Status token
Returned to the calling application; used for /status/{token}/* read-only endpoints.

Read more in the integration guide.