> ## Documentation Index > Fetch the complete documentation index at: https://docs.iinkedsign.com/llms.txt > Use this file to discover all available pages before exploring further. # List You can retrieve a list of an organization members' current packages by calling the `packages/list` endpoint. ## Request ```http Request theme={null} POST /packages/list { "memberId": "e4f0bce5-30fc-43c4-b9ee-364ff5b04dea", "search": null, "types": null, "states": null, "isExecuted": true, "sortBy": "created", "take": 50, "skip": 0 } ``` ### Body Some filters are restricted based on the authentication method used or permissions of the organization member. To filter packages for other members, you must use one of the following authentication methods: To filter packages for teams, the authenticated member must belong to the specified team. The member ID to retrieve packages for. The team ID to retrieve packages for. Filter packages by folder ID. When true, retrieves packages for all members in the organization. Filter packages by search terms. This performs a full text search on package `name`, `description`, `message`, `category`, `client number`, `matter number`, as well as signer and recipient `first name`, `last name`, `email`, and `mobile number`. You can use `*` as a wildcard character to perform suffix matching (e.g., `Contract*` matches any package whose name contains a word starting with "Contract"). Filter packages by package type. | Value | Description | | :------------------- | :---------------------------------------------------------------------------------------------- | | concurrent | **Concurrent**: Allows multiple signers to sign the document simultaneously. | | Sequential | **Sequential**: Requires signers to sign the document in a specific order. | | Counterpart | **Group Send**: Enables group signing, where all signers receive the document at the same time. | | video\_closing\_room | **Video Signing Room**: A virtual room for signing documents via video conference. | | Live Session | **In Person**: An in-person signing session with all parties present. | Even though the signing workflow names have evolved, the constants used to identify them have remained the same. The package type constants are case-sensitive. Ensure that you use the exact casing as shown in the table above when specifying package types in your API requests. Filter packages by package state. New package states may be added in future releases. It is recommended that you always validate your integration against the sandbox before new releases are deployed into production. Release 4.0 introduces two new package states, `executed` and `expired`. In 3.6 both executed and expired packages were in an `open` state. | Value | Version | Description | | :-------- | :------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | draft | 1.0 | Package will be added in a draft state. Notifications will not be sent to the signer(s). You must call the send API, or the package owner must manually send the package from within iinked Sign. | | open | 1.0 | The package will be ready for signing, and notifications will be sent to the signer(s) if enabled. | | executed | 4.0 | The package has been fully executed by all signers. | | expired | 4.0 | The package was not signed by the sign by date and has now expired. VSR packages will expire 7 days after their scheduled meeting date. | | rescinded | 3.5 | The package was rescinded and is no longer available for signing. | | select | 3.6 | Use the select state only when the package will be opened in the **embedded package editor** and you want the workflow to prompt the user to choose a package type. Packages in the select state will be automatically deleted if not converted to draft or open within 24 hours. | | add | 2.9 | Use the add state only when the package will be opened in the **embedded package editor** and you want the workflow to function as if you're creating a new package, rather than editing an existing one. Packages in the add state will be automatically deleted if not converted to draft or open within 24 hours. | When `true` will only return executed packages, when `false` will only return non-executed packages. Leave null to not apply any executed filter. Filter packages whose sign by date is within the next X days. For example, setting `days` to `7` will return packages whose sign by date is within the next 7 days. You can use a negative value to filter packages whose sign by date is in the past. Sort results by one of the following: | Value | Description | | :------------------ | :--------------------------------------------------- | | created | Date package was created (descending). | | last\_modified | Date package was last modified (descending). | | reminder | Date of scheduled reminder (descending). | | signed | Date package was signed by last signer (descending). | | sign\_by | Date package is to be signed by (descending). | | sign\_by\_ascending | Date package is to be signed by (ascending). | Number of packages to return. Number of packages to skip. Used for pagination or infinite scroll. ## Response Array of packages returned. Unique identifier for the package. Unique identifier for the organization that owns the package. Identifier for the member who created/owns the package. Team identifier associated with the package. (optional) Folder identifier where the package is stored. (optional) Set to `true` if the package is shared. Creation time (ISO 8601 date-time). Last modification time (ISO 8601 date-time). Deadline for signing (ISO 8601 date-time). Display name of the package. Category for the package. (optional) Client reference number. (optional) Matter reference number. (optional) Description of the package. (optional) Package type identifier. | Value | Description | | :------------------- | :---------------------------------------------------------------------------------------------- | | concurrent | **Concurrent**: Allows multiple signers to sign the document simultaneously. | | Sequential | **Sequential**: Requires signers to sign the document in a specific order. | | Counterpart | **Group Send**: Enables group signing, where all signers receive the document at the same time. | | video\_closing\_room | **Video Signing Room**: A virtual room for signing documents via video conference. | | Live Session | **In Person**: An in-person signing session with all parties present. | Even though the signing workflow names have evolved, the constants used to identify them have remained the same. The package type constants are case-sensitive. Ensure that you use the exact casing as shown in the table above when specifying package types in your API requests. Current state of the package. New package states may be added in future releases. It is recommended that you always validate your integration against the sandbox before new releases are deployed into production. Release 4.0 introduces two new package states, `executed` and `expired`. In 3.6 both executed and expired packages were in an `open` state. | Value | Version | Description | | :-------- | :------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | draft | 1.0 | Package will be added in a draft state. Notifications will not be sent to the signer(s). You must call the send API, or the package owner must manually send the package from within iinked Sign. | | open | 1.0 | The package will be ready for signing, and notifications will be sent to the signer(s) if enabled. | | executed | 4.0 | The package has been fully executed by all signers. | | expired | 4.0 | The package was not signed by the sign by date and has now expired. VSR packages will expire 7 days after their scheduled meeting date. | | rescinded | 3.5 | The package was rescinded and is no longer available for signing. | | select | 3.6 | Use the select state only when the package will be opened in the **embedded package editor** and you want the workflow to prompt the user to choose a package type. Packages in the select state will be automatically deleted if not converted to draft or open within 24 hours. | | add | 2.9 | Use the add state only when the package will be opened in the **embedded package editor** and you want the workflow to function as if you're creating a new package, rather than editing an existing one. Packages in the add state will be automatically deleted if not converted to draft or open within 24 hours. | Arbitrary external data attached to the package. Documents that belong to the package. Unique identifier for the document. External identifier for the document. (optional) Order/index of the document within the package. Document display name. Original filename uploaded. Set to `true` if the document has been executed. Execution time (ISO 8601 date-time). Signers for the package. Unique identifier for the signer. Signing order index. First name of the signer. Last name of the signer. Email address of the signer. Role of the signer. | Value | Description | | :----- | :---------------------------------------------------------------------- | | signer | Signer | | guest | Guest of VSR or In Person signing that is not a signer of any documents | | host | Host of VSR or In Person signing | Type of the signer. | Value | Description | | :----- | :------------------------------------------------------------------------ | | signer | Signer | | guest | Signer that was added by the host during VSR or In Person signing session | Set to `true` if signer requires identity verification before signing. Set to `true` if the signer has been verified. Set to `true` if the signer is the next in line to sign. Set to `true` if the signer has executed all documents in the signing package. Execution time (ISO 8601 date-time). Recipients related to the package (additional recipients beyond signers). Unique identifier for the recipient. Recipient first name. Recipient last name. Recipient email address. Recipient type. | Value | Description | | :---- | :------------------------------------------------------------- | | cc | Recipient that will be **CC** on package email notifications. | | bcc | Recipient that will be **BCC** on package email notifications. | Set to `true` if the package has been executed. Execution time (ISO 8601 date-time). Total number of packages that match filter criteria. Number of packages returned per request. Number of packages skipped.