# Confirm the business details

> Save the customer's answers to the setup review. Becomes Revnu's memory of the business, exactly as the dashboard review does.

Canonical: https://revnu.com/docs/setup-confirm
Last updated: 2026-10-16

One `{ id, value }` per row from [setup status](https://revnu.com/docs/setup-status.md): the `found` text when it's right, the customer's correction when it isn't, or their answer to a `question` row. `businessName` corrects the name and `extra` is anything else Revnu should know.

```bash
curl -X POST -H "Authorization: Bearer $REVNU_API_TOKEN" -H "content-type: application/json" \
  -d '{"rows":[{"id":"sells","value":"Invoicing for design agencies"},{"id":"neverSay","value":"Never call it accounting software"}]}' \
  https://revnu.com/api/v1/setup/confirm
```

## Body

| Field | Type | Meaning |
|---|---|---|
| `rows` | array, required | Up to 40 `{ id, value }` objects, each value up to 2,000 characters. Ids come from `review.rows`. |
| `businessName` | string | The corrected business name, up to 120 characters. |
| `extra` | string | Anything else Revnu should know, up to 4,000 characters. |

## Response

| Code | Meaning |
|---|---|
| 200 | `{ "ok": true }`. The stage moves to `payment`. |
| 400 | The body isn't the shape above, or has an unknown field. |
| 409 | `rejected` with a `message`: a row id that isn't in the review, a required row left empty, no website yet, or setup already finished. |

After setup, change what Revnu knows in **Settings → Memory**. With the CLI: `revnu setup confirm --keep-found --row <id>=<value>`.

## Frequently asked questions

### Can an agent confirm without asking the customer?

Confirm with the customer first. These answers become what Revnu says about the business, so show the customer the rows and confirm what they agree to.