service_requests.get_matchmaking_answer_file_textRead extracted text from a matching-question attachment. List matching answer files first for file_id. Follow next_offset for more text. Pending or failed extraction does not mean the file is empty. This does not download a file, start processing, or change answers.
- 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 |
|---|---|
file_idStable file id returned by the answer-file list or upload operation. | Yes |
max_charactersSee the input schema for constraints. | No |
offsetSee the input schema for constraints. | 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 |
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 Service requests guide.
