Skip to main content
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 afterwards if you need to read the event back.

​
When to use

  • “Event 123 should be 49,not49, not 3,036.”
  • “Fix the amount on that purchase.”
  • “Clear the amount on that refunded order.” — HTTP-only, see Caveats.
Find the event ID first with list_events, get_event, or 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

​
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

​
Caveats

  • amount is required and cannot clear the amount. Unlike the HTTP endpoint PUT /events/{id}, 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.