> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# update_event

> Correct the amount on an existing conversion event by its numeric ID.

Corrects the `amount` on an existing conversion event by its numeric ID. Returns a confirmation with the `id` and the `amount` that was written — not the full event record. Call [`get_event`](/mcp/tools/get-event) afterwards if you need to read the event back.

## When to use

* *"Event 123 should be $49, not $3,036."*
* *"Fix the amount on that purchase."*
* *"Clear the amount on that refunded order."* — HTTP-only, see [Caveats](#caveats).

Find the event ID first with [`list_events`](/mcp/tools/list-events), [`get_event`](/mcp/tools/get-event), or [`get_contact_journey`](/mcp/tools/get-contact-journey) if you don't have it.

Do not use this to backfill events that never happened, to move an event in time, or to change which contact it belongs to — none of those are possible here.

## Parameters

| Parameter | Type    | Required | Description                                                              |
| --------- | ------- | -------- | ------------------------------------------------------------------------ |
| `id`      | integer | Yes      | The numeric ID of the conversion event to update.                        |
| `amount`  | number  | Yes      | New amount for the event, in the Space currency. Must be `0` or greater. |

## Semantics

Sparse update: fields you pass are replaced, everything else is left as it is. `amount` is the updatable field today. The event's contact, time, name, and attribution are not changed.

* `amount: 49` → the event now carries \$49.
* `amount: 0` → the event now carries \$0 (still counted as a conversion).

## Example response

```json theme={null}
{
  "message": "Event updated successfully",
  "id": "8123",
  "amount": 49
}
```

## Caveats

* **`amount` is required and cannot clear the amount.** Unlike the HTTP endpoint [`PUT /events/{id}`](/api-reference/endpoint/update-event), which accepts `amount: null` to clear the figure, this tool treats `null` as "not provided" — clearing an amount is only possible through the HTTP API.
* Returns a `not_found` error if no event with that ID exists in the current Space, including IDs that belong to another Space.
* The rate limit is the same 60 requests/minute write bucket as the HTTP endpoint.