---
title: "Derived planned-vs-actual-vs-result summary for one outreach. All aggregate counts are computed from the EFFECTIVE execution set and the event ledger, using the same canonical selector as /effective-state, so the two always agree."
method: GET
path: "/outreach/{id}/reconciliation"
---

# Derived planned-vs-actual-vs-result summary for one outreach. All aggregate counts are computed from the EFFECTIVE execution set and the event ledger, using the same canonical selector as /effective-state, so the two always agree.

`GET /outreach/{id}/reconciliation`

## Request

- Base URL: `https://forbiz.io/api/public/agent`
- URL: `https://forbiz.io/api/public/agent/outreach/{id}/reconciliation`
- Auth: HTTP bearer

CANONICAL AGGREGATION RULE: an execution that a later record supersedes is history, and of the rows sharing one external execution identity only the newest is effective. Only effective executions and their target-level observations contribute to current totals (sent_confirmed, not_contactable, delivery statuses, bounce counts derived from execution-target rows, recipient counts, execution summary metrics). A correction is a correction to what Forbiz knows about the same real-world batch, never a second send, so a supersession chain never inflates totals. History is never deleted: superseded and earlier corrected records remain readable via GET /outreach/{id}/executions, where each record carries is_effective, and duplicate_execution_rows_ignored reports how many records were excluded from current truth.

## Path parameters

- `id` string, required

## Response `200`

Reconciliation

- object
  - `outreach` object
  - `summary` object
  - `executions` object[]

## Other responses

- `404`: Not found

---

[API](https://skmtc.dev/forbiz/apis/forbiz-external-agent-api.md) · [All operations](https://skmtc.dev/forbiz/apis/forbiz-external-agent-api/llms.txt) · [OpenAPI document](https://skmtc.dev/forbiz/apis/forbiz-external-agent-api/revisions/e5b10d59dc5f?raw)