Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Path Parameters
A unique string that identifies the envelope in the Nitro system.
A unique string that identifies the document in the Nitro system.
Body
- Checkbox
- Company
- Custom
- Date
- Initials
- Name
- Signature
- Title
Parameters to create a Checkbox field
An array of numbers in the format [x, y, w, h] that defines the field’s bounding box on the page:
x, y
are the coordinates of the top-left corner, measured in points (pt).w, h
are the width and height of the bounding box, also in points (pt).
For more information on calculating positions, see the Bounding Box Guide.
4
elementsThe unique identifier of the participant assigned to the field. Fields can only be created for participants with the signer role.
checkbox
The page number where the field appears. Pages follow 1-based indexing, so the first page is 1.
A boolean that indicates whether the participant must complete the field.
Response
Field created successfully
- Date Field
- Custom Field
- Signature Field
- Name Field
- Checkbox Field
- Initials Field
- Company Field
- Title Field
Create Date Field Response
Enum that specifies which type of information an eSignature participant is expected to fill in.
signature
, name
, checkbox
, date
, initials
, company
, title
, custom
An array of numbers in the format [x, y, w, h] that defines the field’s bounding box on the page:
x, y
are the coordinates of the top-left corner, measured in points (pt).w, h
are the width and height of the bounding box, also in points (pt).
For more information on calculating positions, see the Bounding Box Guide.
4
elementsFor date field types, you can specify the format that will automatically populate when a signer participant opens the document in an envelope.
The default value is the date on which the signer opens the envelope. The signer can manually edit the date after it auto-populates, if needed.
The following date format options are supported (examples use September 10, 2025):
MM/DD/YYYY
→ 09/10/2025MM-DD-YYYY
→ 09-10-2025MMM DD YYYY
→ Sep 10 2025DD/MM/YYYY
→ 10/09/2025DD MMM YYYY
→ 10 Sep 2025DD MMMM YYYY
→ 10 September 2025YYYY/MM/DD
→ 2025/09/10YYYY-MM-DD
→ 2025-09-10YYYY-MMM-DD hh:mm
→ 2025-Sep-10 14:30
The unique identifier of the participant assigned to the field. Fields can only be created for participants with the signer role.
ID of the document to which this field belongs.
The page number where the field appears. Pages follow 1-based indexing, so the first page is 1.
A boolean that indicates whether the participant must complete the field.
A boolean that indicates that the participant can change value of the field. By default the value of the field is current date and the participant can't change the value.
Unique ID of the field