client_intake_applications.request_signatureAfter reviewing the application, confirm the recipient and signature-only or full Edit access. Send a verified sharespace invitation. This does not sign or submit. External MCP must explain the access granted and obtain explicit user confirmation before sending. Reuse idempotency_key for retries. Read the returned request with get_signature_request. The recipient opens signing_url and verifies their email; queued is not proof of delivery.
- Operation
- write
- 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.
Provider portal inputs
| Name and description | Required |
|---|---|
access_modesignature_only permits the requested signature; edit also permits completion and submission. | No |
application_idCopy client_intake_application.id from businesses.get; not the Business ID. Prefix: ciappl_. | Yes |
block_keySignature block_key from get_contract or review_signature. | Yes |
emailSee the input schema for constraints. | Yes |
idempotency_keySee the input schema for constraints. | Yes |
item_idOpaque repeated item_id from repeatable-item tools, if applicable. | No |
messageSee the input schema for constraints. | No |
provider_slugCopy provider_slug from providers.list; named slugs are valid. | Yes |
signature_request_idOnly for an explicitly confirmed resend. Preserve the original block, item, email and access mode; omit message to reuse it. | No |
user_confirmedSee the input schema for constraints. | Yes |
View exact input schema
Result
Check the structured result for success or an error before continuing. Read the affected record to confirm your change.
View exact output schema
For this workflow’s steps and prerequisites, read the Intake applications guide.
