For the complete documentation index, see llms.txt. This page is also available as Markdown.

Envelope Search

This document contains endpoints for searching envelopes and workflows, retrieving mailbox filters, creating reports, and configuring envelope list columns.

Envelope Search endpoints retrieve envelopes available in a specific mailbox and filter them by status, scope, template, dates, recipients, metadata, or searchable field values.

The controller also provides operations for editorial review and approval searches, report creation, template-role discovery, mailbox-folder retrieval, and envelope-list column configuration.

Business goals

Envelope Search endpoints support the following business goals:

  • Find envelopes for operational processing

  • Monitor received, sent, draft, shared, archived, deleted, expiring, or waiting envelopes

  • Find envelopes associated with specific templates, senders, recipients, labels, forms, or metadata

  • Search values stored in searchable envelope fields

  • Retrieve envelopes involved in editorial review or approval workflows

  • Generate reports for selected envelopes or filtered search results

  • Retrieve folders available in a mailbox

  • Configure additional columns displayed in envelope lists

Endpoint summary

Search, review, approval, and reporting

Method
Endpoint
Purpose

POST

/api/v1/envelope/search

Search envelopes available in the current mailbox

POST

/api/v1/envelope/search/roles

Retrieve template roles for envelope search

POST

/api/v1/envelope/search-reviews

Search envelopes associated with editorial reviews

POST

/api/v1/envelope/search-approvals

Search envelopes associated with approval workflows

POST

/api/v1/envelope/report

Request an envelope report

POST

/api/v1/envelope/mailbox-folders

Retrieve available mailbox folders

POST

/api/v1/envelope/fields

Retrieve searchable envelope fields

Displayed columns

Method
Endpoint
Purpose

POST

/api/v1/envelope/column

Add an envelope field as a displayed column

PUT

/api/v1/envelope/column/{id}

Update a displayed column

DELETE

/api/v1/envelope/column

Delete displayed columns

POST

/api/v1/envelope/column-reset

Reset envelope column settings

Request context

All operations require an API token and the current mailbox UUID. The Mailbox header determines which envelopes, workflows, search fields, folders, reports, and column settings are available to the request.

Header
Required
Description

Authorization

Yes

Bearer authorization token

Mailbox

Yes

Current mailbox UUID

Content-Type

Conditional

application/json for requests with a JSON body

POST /api/v1/envelope/column-reset does not have a request body, so its request does not require Content-Type. All other operations described on this page accept a JSON request body.

The mailbox UUID is represented as {mailboxUuid} in request examples. Envelope search responses use the property name mailboxUUID, while sender, initiator, and template-related response objects can use mailboxUuid; integrations must preserve the capitalization defined by each response schema.

Pagination

The following query parameters apply to POST /api/v1/envelope/search, POST /api/v1/envelope/search-reviews, and POST /api/v1/envelope/search-approvals. Use them to control which page is returned or request only envelope identifiers.

Parameter
Type
Required
Default
Description

offset

integer

No

0

Number of envelopes to skip

limit

integer

No

25

Maximum number of envelopes to return

uuidOnly

boolean

No

Not set

Retrieve only envelope UUIDs

Search envelopes

Use POST /api/v1/envelope/search to retrieve envelopes available in the current mailbox. Send an empty JSON object to search without body filters, or provide one or more properties to narrow the results.

Request filters

Property
Type
Description

label

array of strings

Envelope labels

scope

array of strings

Envelope locations

status

array of strings

Envelope statuses

subject

string

Envelope subject

createDateFrom

date-time

Earliest envelope creation date

createDateTo

date-time

Latest envelope creation date

receiveDateFrom

date-time

Earliest envelope receipt date

receiveDateTo

date-time

Latest envelope receipt date

expireDateFrom

date-time

Earliest envelope expiration date

expireDateTo

date-time

Latest envelope expiration date

sendDateFrom

date-time

Earliest envelope sending date

sendDateTo

date-time

Latest envelope sending date

archived

boolean

Archived or non-archived envelopes

deleted

boolean

Deleted or non-deleted envelopes

template

array of UUIDs

Template UUIDs

activeRole

array of strings

Active template roles

sender

array of strings

Envelope senders

recipient

array of strings

Envelope recipients

sortField

string

Field used for sorting, createdAt by default

sort

string

Sort order

searchFields

array of objects

Searchable envelope field values

form

array of UUIDs

Form UUIDs

metadata

object

Metadata key-value properties

templateVersion

array of UUIDs

Template version UUIDs

Supported scope values:

  • inbox — received envelopes

  • outbox — sent envelopes

  • draft — draft envelopes

  • shared — shared envelopes

Supported status values:

  • DRAFT

  • SENT

  • WAITING

  • COMPLETED

  • CANCELLED

  • EXPIRED

  • ON_APPROVAL

Supported sort values:

  • desc — descending

  • asc — ascending

If sortField is omitted, the API uses createdAt. Use asc or desc in sort to control the order.

Retrieve envelopes without body filters

This request returns the first 25 envelopes available in the current mailbox. Change offset and limit to retrieve another page or modify its maximum size.

Retrieve only envelope UUIDs

Set uuidOnly=true when the integration only needs identifiers for subsequent processing. The API retrieves only the UUID of each envelope matching the supplied filters.

Practical example: Find completed envelopes for a customer

A CRM integration can find completed sales agreements created from a specific template for one customer. The request filters the mailbox outbox by status, template UUID, creation date, and the customer identifier stored in envelope metadata.

The metadata object accepts one or more string key-value properties. Use metadata names and values stored in the target envelopes.

A successful request returns 200 OK with a paginated collection. Save the returned envelopeUuid values for status checks, downloads, reports, or other follow-up operations.

The response contains the envelope page together with values that can be used to build search and display controls. The following collections describe the returned envelopes, searchable fields, configured columns, senders, and templates.

Property
Description

data

Envelopes returned for the current page

searchFields

Searchable envelope fields available in the results

columns

Current envelope-list column configuration

senders

Senders represented in the results

templates

Templates represented in the results

sendersInfo

Additional sender information

templatesInfo

Additional template information

Search by envelope field value

The searchFields property searches values stored in template fields configured as searchable. First use POST /api/v1/envelope/fields to retrieve available field names and types, then use the returned values in POST /api/v1/envelope/search.

Each searchFields object supports the following properties:

Property
Type
Required
Description

name

string

Yes

Field name, minimum one character

value

string

No

String field value

number

number

No

Numeric field value

from

date-time

No

Beginning of a date-time range

to

date-time

No

End of a date-time range

checked

boolean

No

Checkbox value

type

string

No

Searchable field type

Use the value property corresponding to the field type. For example, use value for text fields, number for numeric fields, from and to for date ranges, and checked for checkbox fields.

Find searchable fields

The required name query parameter contains the field-name term. The request body uses the standard envelope filters to limit the envelopes from which searchable fields are retrieved.

A successful request returns 200 OK with the matching field names and types. The response can contain multiple searchable fields.

Search by the returned field

Use the exact returned field name and type in searchFields. Supply the search value through the property corresponding to that type.

Add from and to to search a date-time range:

Retrieve template roles for filtering

Use POST /api/v1/envelope/search/roles to retrieve role values from selected templates. The returned role values can then be used in the activeRole property of an envelope search request.

A successful request returns 200 OK with the roles found in the selected templates. Use the returned role names without changing their capitalization.

The following filter finds envelopes in which Signer is currently active. It also limits the results to the template from which the role was retrieved.

Search envelopes for editorial review

Use POST /api/v1/envelope/search-reviews to retrieve envelopes associated with editorial review workflows. The request can filter reviews by scope, status, template, initiator, participant, receipt date, or subject.

Request filters

Property
Type
Description

scope

array of strings

Editorial review scopes

status

array of strings

Editorial review statuses

subject

string

Envelope subject

receiveDateFrom

date-time

Earliest envelope receipt date

receiveDateTo

date-time

Latest envelope receipt date

template

array of UUIDs

Template UUIDs

initiator

array of UUIDs

Review initiator mailbox UUIDs

participant

array of UUIDs

Editorial review participant UUIDs

sort

string

Sort order

Supported editorial review scopes:

  • inbox

  • outbox

Supported editorial review statuses:

  • WAITING

  • ON_APPROVAL

  • COMPLETED

  • CANCELLED

Practical example: Find reviews waiting for a participant

This request retrieves incoming editorial reviews that are waiting for a selected participant. The template filter limits the results to one document workflow.

A successful request returns 200 OK with a paginated collection. Each result includes the envelope UUID, review status, progress values, template information, approval flow UUID, urgent indicator, and last update time.

Search envelopes for approval

Use POST /api/v1/envelope/search-approvals to retrieve envelopes associated with approval workflows. The request can filter approvals by scope, status, template, initiator, urgency, receipt date, or subject.

Request filters

Property
Type
Description

scope

string

Approval search scope

status

array of strings

Approval statuses

subject

string

Envelope subject

receiveDateFrom

date-time

Earliest envelope receipt date

receiveDateTo

date-time

Latest envelope receipt date

template

array of UUIDs

Template UUIDs

initiator

array of UUIDs

Approval initiator mailbox UUIDs

sort

string

Sort order

urgent

boolean

Urgent approval indicator

Supported approval scopes:

  • inbox

  • outbox

Supported approval statuses:

  • NOT_STARTED

  • WAITING

  • APPROVED

  • REJECTED

  • CANCELLED

Practical example: Find urgent approvals

This request retrieves urgent incoming approval workflows that have not started. The template filter limits the results to the selected business process.

A successful response contains the matching envelopes together with the initiators and templates represented in the results. Each result includes the envelope UUID, approval flow UUID, current status, progress values, and urgent indicator.

Retrieve mailbox folders

Use POST /api/v1/envelope/mailbox-folders to retrieve folder values available for the current mailbox. Send the folder values to check in a JSON array. The response returns the available values.

Supported folder values:

  • INBOX

  • OUTBOX

  • DRAFT

  • ARCHIVED

  • DELETED

  • SHARED

  • EXPIRING

  • WAITING

  • EVERYTHING

A successful request returns 200 OK with the available folder values. These values can be used to build mailbox navigation or determine which envelope collections are available in the current mailbox.

Request an envelope report

Use POST /api/v1/envelope/report to request a report for specific envelope UUIDs or for envelopes matching search parameters. The request schema requires uuids and searchParams to be specified separately, so provide only one of these properties in each request.

Create a report for selected envelopes

Create a report from search filters

A successful request returns 201 Created, confirming that DocStudio accepted the report request. The Swagger operation does not define a response body or a separate report-retrieval endpoint for this operation.

Configure displayed envelope columns

Column endpoints manage additional envelope fields displayed in the mailbox envelope list. The configuration belongs to the mailbox supplied in the Mailbox header and is returned in the columns property of an envelope search response.

The create request uses fieldName to identify the searchable envelope field that should become a column. Column responses use name for the resulting display name, while type identifies how the field value is represented.

Add a displayed column

Use POST /api/v1/envelope/column to add a searchable envelope field as a displayed column. Save the returned UUID because it is required to update or delete the column.

Property
Type
Required
Description

fieldName

string

Yes

Searchable field name

type

string

Yes

Searchable field type

order

integer

No

Position of the column

visible

boolean

No

Column visibility

width

integer

No

Column width

Supported type values:

  • text

  • datetime

  • selectDictionary

  • einksign

  • initials

  • pades

  • number

  • money

  • lookup

  • duplicate

  • attachment

  • formula

  • numberToText

  • autonumber

  • checkbox

  • dropdown

  • radio

  • barcode

A successful request returns 201 Created with the displayed column UUID. Use this UUID as {id} when updating the column or include it in extraFieldUuids when deleting columns.

Update a displayed column

Use PUT /api/v1/envelope/column/{id} to change the column order, visibility, or width. The {id} path parameter is the displayed column UUID returned by the create operation.

A successful request returns 200 OK. The Swagger operation does not define a response body for this endpoint.

Delete displayed columns

Use DELETE /api/v1/envelope/column to remove one or more additional columns. Send the displayed column UUIDs in the extraFieldUuids request property.

A successful request returns 200 OK. The Swagger operation does not define a response body for this endpoint.

Reset column settings

Use POST /api/v1/envelope/column-reset to reset the envelope-list column settings for the current mailbox. This operation changes the current column configuration, so retrieve and save the existing columns collection through POST /api/v1/envelope/search first if it may be needed later.

A successful request returns 200 OK with the resulting column configuration. Each object contains the column UUID, name, type, order, visibility, and width.

Last updated

Was this helpful?