---
title: "Create Envelope"
method: POST
path: "/sign/envelopes"
tags: ["Sign"]
---

# Create Envelope

`POST /sign/envelopes`

The **Create Envelope** endpoint creates a new **sign envelope** in Nitro.

A **sign envelope** is the container for signature processes in Nitro. It can include assets such as documents, participants, signature fields, and configuration settings that define how the signing process should behave.
With the Create Envelope endpoint, you will create an empty sign envelope you can later add assets to.

## Request body

- EnvelopeCreate
  - `name` string, required — The Envelope's name. It doesn't have to be unique.
  - `notification` Notification
    - `subject` string, required — The subject line of the notification email.
    - `body` string, required — The body content of the notification email.
  - `mode` 'sequential' | 'parallel', required — The Signing Mode in an enum that defines the signing order. It has two possible values: - `sequential`: Participants receive notifications one at a time, in the order they were added to the envelope. Each new notification is triggered once the previous participant has completed their signing. - `parallel`: All participants are notified at the same time and can sign the documents in the envelope independently, without waiting for others.
  - `notificationsManagedBy` 'nitro' | 'sender' — Who notifies the participants of this envelope. Two values are accepted: - `nitro` (default): Nitro sends the participant notification emails, as it always has. - `sender`: Nitro sends **no** automated email notifications to signers or CC recipients — including signature requests, reminders and signature completion notices. You distribute the signing links yourself, using the *List Signer Signing URLs by Envelope ID* endpoint and the envelope webhooks. When set to `sender`, the `notification` object must be omitted — its `subject` and `body` would never be rendered, so sending both is rejected with a `400`. When it is omitted or set to `nitro`, the `notification` object is required. **This setting is only available to API applications.** By enabling this setting, you assume full responsibility for notifying signers and CC recipients of pending signature requests, deadlines, and completed documents through your own communication channels. Nitro Sign will not notify these participants on your behalf under any circumstances while this setting is enabled. Depending on your use case and jurisdiction, failure to adequately notify signers may affect the enforceability of the resulting electronic signature or your compliance obligations under applicable e-signature laws (e.g., ESIGN Act, UETA, eIDAS). We strongly recommend consulting your legal or compliance team before enabling this setting in production. This setting requires SMS authentication to be configured for all signers on the envelope, as an additional safeguard against unauthorized access to signing links. Sending the envelope for signing fails if any signer is missing it.

## Response `201`

When an envelope is created you will get a unique ID for it. You can add assets to the envelope later by referencing its unique ID using other endpoints in this API.

- ExtendedEnvelope
  - `ID` string, uuid — A unique UUIDv4 string that identifies the envelope in the Nitro system.
  - `createdAt` string, date-time — UTC timestamp indicating when the envelope was created.
  - `lastModifiedAt` string, date-time — UTC timestamp indicating the last time the envelope was updated. Matches `createdAt` at the time of creation.
  - `name` string — The name of the envelope.
  - `status` 'drafted' | 'sent' | 'processing' | 'sealed' | 'rejected' | 'cancelled' | 'deleted' — The internal status of the envelope. Defaults to drafted on creation.
  - `mode` 'sequential' | 'parallel' — Signing mode for the envelope.
  - `notification` Notification
    - `subject` string, required — The subject line of the notification email.
    - `body` string, required — The body content of the notification email.
  - `notificationsManagedBy` 'nitro' | 'sender' — Who notifies the participants of this envelope: `nitro` or `sender`. Defaults to `nitro`.

## Other responses

- `400` — Invalid envelope or document name
- `401` — Unauthorized - Invalid or missing JWT token

## Changes

- **2026-08-27** `7b97ae457833` — 1 info
  - the request property `notification` became optional
- **2026-08-24** `e6b46ba50304` — 2 info
  - added the new optional request property `notificationsManagedBy`
  - added the optional property `notificationsManagedBy` to the response with the `201` status

[Change history](https://skmtc.dev/gonitro/apis/nitro-sign-public-api/changes/sign/envelopes/post.md)

---

[API](https://skmtc.dev/gonitro/apis/nitro-sign-public-api.md) · [All operations](https://skmtc.dev/gonitro/apis/nitro-sign-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/gonitro/nitro-sign-public-api/revisions/7b97ae457833/schema)