deal_applications.get_signature_requestRead this application's native signature requests and latest invitation attempt. These requests concern signature blocks, not signed-PDF upload questions. Search matches recipient email; ordering supports created_at. Completed means the requested recipient signed that exact entry; accepted delivery means mail-provider acceptance, not inbox delivery. The recipient opens signing_url and verifies their email. After completion check application readiness. If an invitation failed and your available tools cannot request signatures, ask the requester to resend it. An empty list does not satisfy a signature requirement. Never sign through answer updates.
- 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.
Inputs
| Name and description | Required |
|---|---|
application_idDeal Application id returned by deals.get or deals.create. Prefix: dapp_. | Yes |
provider_slugPortal workspace where the Deal Application is available. Copy provider_slug from providers.list; named slugs are valid. | Yes |
signature_request_idSee the input schema for constraints. | Yes |
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.
