deal_applications.get_submission_packageCheck whether an original submission was saved, when it was submitted, and which files are available.
Next steps
- Use
list_submission_filesto find supporting documents. - Use
get_submission_downloadfor the original PDF, ZIP or an individual file. - Use
frontend_linkto open provider Application details or the client application workspace. The saved copy appears in the submission timeline/history.
preparation_status describes the saved copy, not delivery or current application status. Compare its retained files with current attachments when checking for missing submitted documents; neither inventory proves the recipient received or reviewed them. not_captured means no original exists. This summary contains no submitted answers; review the original PDF. Never substitute current answers for the original or submit again to obtain a copy.
- 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.
Provider portal 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 |
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.
