Record the mapping answer
prepress_confirmRecord the customer's approval of a PROPOSED mapping. The mapping
carries an APPROVE_MAPPING confirmation in pending_confirmations, and
answering it here with the approve option is what unlocks
prepress_submit_mapping.
confirmation_id and option_id must both be copied verbatim from the
confirmation — option_id is the listed option, never a phrase the
customer typed and never a value you compose. If the customer does not
want this mapping, do not answer the confirmation: call
prepress_map_pages with the positions they ask for, or ask for
corrected files.
Returns a job_id. The result is the same shape as prepress_map_pages.
Job errors: ConfirmationNotFoundError (already answered, or wrong id),
InvalidAnswerError (option not on that confirmation), AlreadyMappedError
(this item already went through the one-way door), or ItemHasDesignError
(the item holds an attached design, which is what prints).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"session_id": "<session_id>",
"order_id": "<order_id>",
"item_id": "<item_id>",
"confirmation_id": "<confirmation_id>",
"option_id": "<option_id>"
},
"name": "prepress_confirm"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| item_id | Yes | ||
| order_id | Yes | ||
| option_id | Yes | ||
| session_id | Yes | ||
| confirmation_id | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |