deal_applications.list_signature_requestsList native signature requests with pagination. Search matches recipient email; ordering supports created_at. Requests concern signature blocks, not signed-PDF upload questions. Completed means the recipient signed the exact entry; accepted delivery means mail-provider acceptance, not inbox delivery. A pending request with active access may include signing_url for recipient email verification and human signing. This read does not sign, resend, submit or satisfy an incomplete signature requirement.
- Operation
- read
- OAuth scopes
- mcp
Availability depends on your assigned tools. Scopes do not grant record access. Read the tool description and current resource before changing it; follow the required revision and idempotency fields below.
Client portal inputs
| Name and description | Required |
|---|---|
application_idApplication ID from client_workspace.get in this workspace; not the Business ID. | Yes |
cursorSee the input schema for constraints. | No |
orderingSee the input schema for constraints. | No |
organization_slugSee the input schema for constraints. | Yes |
page_sizeSee the input schema for constraints. | No |
provider_slugSee the input schema for constraints. | Yes |
searchSee the input schema for constraints. | No |
View exact input schema
Provider portal inputs
| Name and description | Required |
|---|---|
application_idDeal Application id returned by deals.get or deals.create. Prefix: dapp_. | Yes |
cursorSee the input schema for constraints. | No |
orderingSee the input schema for constraints. | No |
page_sizeSee the input schema for constraints. | No |
provider_slugPortal workspace where the Deal Application is available. Copy provider_slug from providers.list; named slugs are valid. | Yes |
searchSee the input schema for constraints. | No |
View exact input schema
Result
Check the structured result for success or an error before continuing.
View exact output schema
For this workflow’s steps and prerequisites, read the Deal applications guide.
