client_intake_applications.get_answer_file_downloadDownload an original uploaded file from the intake form. List files first and pass its file id. For a download result, GET its five-minute URL with transfer_token as a Bearer credential; no separate API key is needed. If staged_file is returned instead, use it with download_attachment. Keep transfer credentials private. This does not change the application's file.
- 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 |
file_idStable file id returned by the answer-file list or upload operation. | Yes |
organization_slugSee the input schema for constraints. | Yes |
provider_slugSee the input schema for constraints. | Yes |
View exact input schema
Provider portal inputs
| Name and description | Required |
|---|---|
application_idCopy client_intake_application.id from businesses.get; not the Business ID. Prefix: ciappl_. | Yes |
file_idStable file id returned by the answer-file list or upload operation. | Yes |
provider_slugCopy provider_slug from providers.list; named slugs are valid. | 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 Intake applications guide.
