---
title: "Accept Suggestion"
method: POST
path: "/api/reconciliation/suggestions/{suggestion_id}/accept"
tags: ["reconciliation"]
---

# Accept Suggestion

`POST /api/reconciliation/suggestions/{suggestion_id}/accept`

## Request

- Base URL: `https://demo.usesecuro.com` (the document declares no server; this is the origin it was published from)
- URL: `https://demo.usesecuro.com/api/reconciliation/suggestions/{suggestion_id}/accept`
- Auth: OAuth 2
  - Password
  - Token URL: `/api/auth/login`
- TypeScript: <https://skmtc.dev/usesecuro/apis/securo/docs/api/reconciliation/suggestions/:suggestion_id/accept/post.ts> (a function with typed inputs; its response is checked against the schema)

Take the match, and write it the way its kind is written.

An invoice gets an allocation; a recurring bill gets the charge bound
to it. The two are genuinely different writes, which is why the
suggestion service marks and this route links.

**A payment offered against several invoices is accepted whole.** The
question was "does this cover these three", so answering it two thirds
of the way would leave the payment short on the rest with nothing
having warned anybody. All the writes happen inside one savepoint: if
the last invoice refuses, the first two are not left standing.

## Path parameters

- `suggestion_id` string, uuid, required

## Headers

- `X-Workspace-Id` string, nullable

## Response `200`

Successful Response

- SuggestionRead: One open question, with the evidence behind it. `scores` is the per-signal breakdown rather than one number, because "we are 78% sure" is not something anyone can check, while "the amount is exact and the date is four days out" is.
  - `id` string, uuid, required
  - `node` string, required
  - `strategy_id` string, required
  - `expectation_kind` string, required
  - `expectation_id` string, uuid, required
  - `expectation_label` string, nullable
  - `amount` string, required
  - `scores` object, required
  - `status` string, required
  - `created_at` string, date-time, required
  - `transaction` SuggestionTransactionRead
    - `id` string, uuid, required
    - `description` string, nullable
    - `amount` string, required
    - `currency` string, nullable
    - `date` string, date, required
    - `type` string, required
    - `account_id` string, uuid, nullable
  - `covers` SuggestionCovers[]
    - `expectation_kind` string, required
    - `expectation_id` string, uuid, required
    - `label` string, nullable
    - `amount` string, required

## Other responses

- `422`: Validation Error

## Changes

- **2026-11-05** `416a7752fec4`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/usesecuro/apis/securo/changes/api/reconciliation/suggestions/:suggestion_id/accept/post.md)

---

[API](https://skmtc.dev/usesecuro/apis/securo.md) - [All operations](https://skmtc.dev/usesecuro/apis/securo/llms.txt) - [OpenAPI document](https://skmtc.dev/usesecuro/apis/securo/revisions/416a7752fec4?raw)