service_requests.prepare_matchmaking_answer_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 to a file question in funding request matching application; preparation attaches nothing. Requires the question block_key, current answers_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 plus application limits. The upload receipt and current file inventory establish attachment completion. Identical byte transfers can retry the valid credential; a new upload needs a new key and current revision. Uncertain outcomes require inventory verification.
- 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.
Client portal inputs
| Name and description | Required |
|---|---|
block_keyCopy block_key from the owning application’s get_contract question blocks; projects use get_matchmaking_application_contract. | Yes |
content_sha256SHA-256 of the exact file bytes to POST; not a document config digest. | Yes |
expected_answers_revisionSee the input schema for constraints. | Yes |
filenameSee the input schema for constraints. | Yes |
idempotency_keySee the input schema for constraints. | Yes |
item_idCopy item_id from the owning application’s repeatable-item list; omit/null for a non-repeatable file question. | No |
organization_slugSee the input schema for constraints. | Yes |
provider_slugSee the input schema for constraints. | Yes |
service_request_slugStable public identifier for the referenced resource. | 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. Read the affected record to confirm your change.
View exact output schema
For this workflow’s steps and prerequisites, read the Service requests guide.
