# Suggest Added Sugars Answers

{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}

Suggests an answer for each requested open Added Sugars row of the recipe and saves the suggestions on the report in ONE new version, for a person to accept, edit or override. A suggestion is a proposal: it appears on the row as `suggested` and counts in the report's `readiness.suggested_rows`, and no row is answered until a person accepts it (`accept_suggestion`). Rows a person has already answered are never changed. A row that already carries a current suggestion is returned as it is (`already_suggested_row_ids`) and not run, saved or charged again, so asking twice costs once; send `refresh: true` to replace it. The response is the updated report in the shape of reading it, with `suggested_row_ids`, `left_open` and `config_version` in `data`.

Rows beyond the request's allowance, rows whose food record could not be found and rows no suggestion settled get no suggestion and are returned in `left_open` for the person to answer. When no row gets a suggestion nothing is saved and `version_id` is the current version.

Every row is named by its ingredient row id (`irow_...`), the id of one ingredient row of this recipe and the id used to answer that row.

Send the recipe's current `version_id` in the `If-Match` header. A stale token is refused before any suggestion is made or charged.

The operation is served only while suggestions are switched on; otherwise it answers 403 `suggester_not_enabled`.

You are charged one credit per row that returns a confident or unsure suggestion that was saved. Rows left open, and rows that need a value from the supplier, are not charged.
