Upload a document to create a new contract template version. The file is validated and stored, a template version is created in DRAFT status, and the document is registered with the signing provider so its signer roles and fields can be detected. Returns the created template version, including its detected roles, fields, and variable placeholders.

This is a multipart form upload, not a JSON request.

Authentication & access

• Requires a client API token: Authorization: Bearer <token>.
• The caller must hold the contracts.templates.write permission and have the OWNER, OPERATIONS, or DEVELOPER role.
• The client must have contract signing enabled. If the feature is disabled the request returns 403.

Request body (multipart/form-data)

File constraints

• Only PDF and DOCX documents are accepted; the extension must be .pdf or .docx.
• The file content must actually match the declared type (a content check rejects a mismatched or corrupt file).
• The file must be non-empty and must not exceed the configured maximum upload size.

Response

200 — The template version was created in DRAFT status. The payload is the template version, including:

• id, name, status (DRAFT), and file_type.
• external_id, signing_template_id, and signing_template_slug.
• the source file metadata under source_file.
• roles — signer roles detected in the document.
• fields — fields detected in the document.
• detected_variables — variable placeholders found in the document.

After creating a template, use the builder session endpoint to configure field placements and signer roles before publishing.

Error responses

Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.