projects.prepare_matchmaking_application_autofill_file_uploadRequires HTTP access to the original bytes. Import from host-provided file input is an alternative when direct transfer is unavailable. Prepare a five-minute upload of an Autofill supporting document. Requires current preparation revision, filename, byte count, SHA-256 and UUID idempotency key. The returned HTTP contract accepts multipart field file with transfer_token as Bearer credential; no separate API key. Limit: 25 MiB. Preparation attaches nothing and does not start Autofill or change answers. The upload receipt and current preparation establish completion. Identical bytes can retry a valid credential; new uploads need a new key and current revision. Uncertain outcomes require preparation verification before another transfer.
- 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.
Inputs
| Name and description | Required |
|---|---|
content_sha256SHA-256 of the exact file bytes to upload. | Yes |
expected_preparation_revisionRead Autofill preparation first and copy its revision. | Yes |
filenameSee the input schema for constraints. | Yes |
idempotency_keySee the input schema for constraints. | Yes |
provider_slugCopy provider_slug from providers.list; named slugs are valid. | Yes |
size_bytesSee the input schema for constraints. | Yes |
workspace_slugMatching workspace: copy workspace_slug (mmw_) from projects.get or projects.list; not project_slug. | 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 Matchmaking guide.
