API v1 is deprecated. For new integrations, please use API v2.
Overview
Fields are interactive elements placed on document pages that recipients need to fill out or sign. Each field is assigned to a specific recipient and positioned using percentage-based coordinates.Field Object
Properties
| Field | Type | Description |
|---|---|---|
id | number | Unique field identifier |
documentId | number | ID of the parent document |
recipientId | number | ID of the recipient assigned to this field |
type | string | Field type (see Field Types) |
pageNumber | number | Page number (1-indexed) |
pageX | number | X position as percentage (0-100) |
pageY | number | Y position as percentage (0-100) |
pageWidth | number | Width as percentage of page (0-100) |
pageHeight | number | Height as percentage of page (0-100) |
customText | string | Value entered by recipient |
fieldMeta | object | null | Type-specific configuration |
inserted | boolean | Whether field has been completed |
Field Types
Signature Fields
| Type | Description | Auto-filled |
|---|---|---|
SIGNATURE | Full signature (drawn, typed, or uploaded) | No |
FREE_SIGNATURE | Unrestricted signature field | No |
INITIALS | Recipient’s initials | No |
Auto-filled Fields
| Type | Description | Value |
|---|---|---|
NAME | Recipient’s full name | From recipient object |
EMAIL | Recipient’s email | From recipient object |
DATE | Current date when field is completed | Auto-generated |
Form Fields
| Type | Description | Validation |
|---|---|---|
TEXT | Free-form text input | Optional |
NUMBER | Numeric input | Optional min/max |
CHECKBOX | Multiple selections | Required items |
RADIO | Single selection from options | Required |
DROPDOWN | Dropdown selection | Required |
Add Field
Add one or more fields to a document in DRAFT status.Path Parameters
| Parameter | Type | Description |
|---|---|---|
id | number | The document ID |
Request Body
You can add a single field or multiple fields in one request: Single Field:| Field | Type | Required | Description |
|---|---|---|---|
recipientId | number | Yes | ID of recipient for this field |
type | string | Yes | Field type |
pageNumber | number | Yes | Page number (1-indexed) |
pageX | number | Yes | X position (0-100) |
pageY | number | Yes | Y position (0-100) |
pageWidth | number | Yes | Width (0-100) |
pageHeight | number | Yes | Height (0-100) |
fieldMeta | object | No | Type-specific options |
Positioning Guide
Field positions use percentages relative to the PDF page:pageX: Horizontal position from left edge (0 = left, 100 = right)pageY: Vertical position from top edge (0 = top, 100 = bottom)pageWidth: Field width as percentage of page widthpageHeight: Field height as percentage of page height
Code Examples
- Tab Title
- Tab Title
Response
fields property.
You can only add fields to documents in DRAFT status. Once sent, fields cannot be added or modified.
Update Field
Update a field’s position or configuration before the document is sent.Path Parameters
| Parameter | Type | Description |
|---|---|---|
id | number | The document ID |
fieldId | number | The field ID |
Request Body
All fields are optional. Only include what you want to update:| Field | Type | Description |
|---|---|---|
recipientId | number | Reassign to different recipient |
type | string | Change field type |
pageNumber | number | Move to different page |
pageX | number | Update X position |
pageY | number | Update Y position |
pageWidth | number | Update width |
pageHeight | number | Update height |
fieldMeta | object | Update configuration |
Code Examples
- Tab Title
- Tab Title
Response
Returns the updated field object.Remove Field
Delete a field from a document in DRAFT status.Path Parameters
| Parameter | Type | Description |
|---|---|---|
id | number | The document ID |
fieldId | number | The field ID |
Code Examples
- Tab Title
- Tab Title
Response
Returns the deleted field object.Field Metadata
Different field types support different metadata configurations.Text Field Metadata
Number Field Metadata
Checkbox Field Metadata
Radio Field Metadata
Dropdown Field Metadata
Signature Field Metadata
Common Field Patterns
Standard Signature Block
Form with Validation
Complete Example
Best Practices
1. Group Related Fields
Add all fields for a recipient in a single batch request:2. Use Consistent Positioning
Maintain consistent alignment and spacing:3. Validate Field Metadata
Ensure metadata matches the field type:4. Test Field Positions
Before sending to recipients, test field positioning:- Create a test document
- Add fields
- Use the signing URL to preview
- Adjust positions as needed
- Delete the test document
See Also
- Documents API - Create and send documents
- Recipients API - Manage recipients
- Templates API - Reusable field configurations
