deal_application_editor.validate_config_fileReview a host-provided UTF-8 JSON form config, up to 1 MiB, without saving. Read get_config_schema and get_config first, then supply the exact filename, byte size, SHA-256 digest and current revisions. Review findings and stored-answer impact before replace_from_config_file with the returned private validation_token. No publication or notifications occur. If file input is unavailable, use prepare_config_validation or the existing application editor. This toolset requires a specific grant and is not assigned by default; request access through Support.
- 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 |
|---|---|
content_sha256SHA-256 fingerprint of the exact document content. | Yes |
deal_idExact Deal id from deals.list or deals.get in the selected provider workspace; do not pass an application or runtime ID. | Yes |
expected_draft_revisionCopy draft_revision from the same current action review. | Yes |
expected_live_revisionCopy live_revision from the current action review. | Yes |
fileSee the input schema for constraints. | Yes |
filenameSee the input schema for constraints. | Yes |
provider_slugProvider workspace returned by providers.list. | Yes |
size_bytesSee 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 application editor guide.
