---
title: "act: correct"
description: "the id of the wrong event, and the right facts to a correcting event"
section: reference
address: /reference/act/correct
contract: 0476e35e6e275db5
---

# act: correct

the id of the wrong event, and the right facts to a correcting event

[figure: The caller sends CorrectInput to /v1/act/correct. The platform returns a card whose body is Event.]

<span class="op-method">POST</span><span class="op-path">/v1/act/correct</span>

Correct an event. The call needs the strategy rung under a token with the act grant, and it is served by the platform.

The route takes [CorrectInput](/concepts/correctinput) and returns a card whose body is [Event](/concepts/event).



## Request body
The request body is [CorrectInput](/concepts/correctinput).



| field | type | required | note |
|---|---|---|---|
| `event` | `id` | yes |  |
| `correction` | [Event](/concepts/event) | yes |  |
| `why` | `text` | yes |  |



## Response
The route returns a card whose body is [Event](/concepts/event). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

## Headers


| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/<id>, then /brand/<id>, then /strategy/<id> |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |



A caller needs the strategy rung and a token with the act grant. The platform serves this route.

## Example
The example sends the smallest body that CorrectInput allows. The build validates it against the schema of CorrectInput.

<details class="wire"><summary>Example</summary>





```sh
curl -X POST https://api.scaleintelligence.co/v1/act/correct \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "event": "…", "correction": { "flow": "…", "unit": "…", "at": "…", "by": { "kind": "a user", "came_in_through": "a session", "access_scopes": [], "tenant": "…", "grants": [] }, "plane": "tenant plane", "outcome": "…", "run": "…" }, "why": "…" }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.act.correct({
    "event": "…",
    "correction": {
      "flow": "…",
      "unit": "…",
      "at": "…",
      "by": {
        "kind": "a user",
        "came_in_through": "a session",
        "access_scopes": [],
        "tenant": "…",
        "grants": []
      },
      "plane": "tenant plane",
      "outcome": "…",
      "run": "…"
    },
    "why": "…"
  });
// answer.body is a Event. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/correct",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "event": "…",
      "correction": {
        "flow": "…",
        "unit": "…",
        "at": "…",
        "by": {
          "kind": "a user",
          "came_in_through": "a session",
          "access_scopes": [],
          "tenant": "…",
          "grants": []
        },
        "plane": "tenant plane",
        "outcome": "…",
        "run": "…"
      },
      "why": "…"
    }).json()
```




```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/correct")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&CorrectInput { /* the fields of the page */ }).send().await?.json().await?;
```




</details>

## MCP tool
The MCP tool `si.act.correct` takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/Event`. The [tool's page](/reference/tools/si-act-correct) describes it.
