---
title: "Search for specific sets of envelopes by using search filters."
method: GET
path: "/v2.1/accounts/{accountId}/envelopes"
tags: ["Envelopes"]
---

# Search for specific sets of envelopes by using search filters.

`GET /v2.1/accounts/{accountId}/envelopes`

This method lets you [search for envelopes](/docs/esign-rest-api/esign101/concepts/envelopes/search/) in your accounts. A large set of filters let you narrow the scope of your search by date, by envelope ID, or by status codes. Your request must include one or more of the following parameters:

* `from_date`
* `envelope_ids`
* `transaction_ids`

### Restrictions

The number of envelopes returned is limited to 1,000 per call. To retrieve the next or previous set of envelopes, use the `nextUri` and `previousUri` parameters returned in the original call's response.

If no `from_date` query parameter is specified, envelopes from more than two years ago will not be returned. To fetch older envelopes, set the specific date range using the `from_date` and `to_date` parameters.

To avoid unnecessary database queries, the Docusign signature platform first checks requests to ensure that the filter set supplied does not result in a zero-size response before querying the database.

### Envelope statuses

This table shows the valid current envelope statuses (`status` parameter) for the different status qualifiers (`from_to_status` parameter) in the request. If the status and status qualifiers in the API request do not contain any of the values shown in the Valid Current Statuses column, then an empty list is returned.

Client applications should check that the statuses (`status` parameter) they are requesting make sense for a given `from_to_status` parameter value.

| Status Qualifier<br>(`from_to_status`) | Effective Status Qualifier | Valid Current Statuses                                                      |
| :------------------------------------- | :------------------------- | :-------------------------------------------------------------------------- |
| any (changed)                          | StatusChanged              | any, created, sent, delivered, signed, completed, declined, voided, deleted |
| created                                | Created                    | any, created, sent, delivered, signed, completed, declined, voided, deleted |
| sent                                   | Sent                       | any, sent, delivered, signed, completed, declined, voided, deleted          |
| delivered                              | StatusChanged              | any, delivered, signed, completed, declined, voided, deleted                |
| signed                                 | StatusChanged              | any, signed, completed, declined, voided, deleted                           |
| completed                              | Completed                  | any, completed, declined, voided, deleted                                   |
| declined                               | StatusChanged              | any, declined, voided, deleted                                              |
| timedout<br>always return zero results | StatusChanged              | any, voided, deleted                                                        |
| voided                                 | Voided                     | any, voided, deleted                                                        |
| deleted                                | StatusChanged              | any, deleted                                                                |

### Extraneous results

In some cases, a request for a specific envelope status will
include envelopes with additional statuses. For example, in
a request with a `from_date` of 2017-01-01, a `to_date` of
2017-01-07 and the status qualifier (`from_to_status`) set
to `delivered`, the response set might contain envelopes
that were created during that time period, but not delivered
during the time period. As a workaround, check the envelope
status values in the result set as needed.


### Related topics

- [Searching for envelopes](/docs/esign-rest-api/esign101/concepts/envelopes/search/)
- [How to list envelope status changes](/docs/esign-rest-api/how-to/list-envelope-status-changes/)

## Path parameters

- `accountId` string, required

## Query parameters

- `ac_status` string
- `block` string
- `cdse_mode` string
- `continuation_token` string
- `count` string
- `custom_field` string
- `email` string
- `envelope_ids` string
- `exclude` string
- `folder_ids` string
- `folder_types` string
- `from_date` string
- `from_to_status` string
- `include` string
- `include_purge_information` string
- `intersecting_folder_ids` string
- `last_queried_date` string
- `order` string
- `order_by` string
- `powerformids` string
- `query_budget` string
- `requester_date_format` string
- `search_mode` string
- `search_text` string
- `start_position` string
- `status` string
- `to_date` string
- `transaction_ids` string
- `user_filter` string
- `user_id` string
- `user_name` string

## Response `200`

Successful response.

## Other responses

- `400` — Error encountered.

---

[API](https://skmtc.net/docusign/apis/docusign-esignature-rest-api.md) · [All operations](https://skmtc.net/docusign/apis/docusign-esignature-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/docusign/docusign-esignature-rest-api/versions/77f1998c313d/schema)