WRITE · 3 operations · may change data
manage_transactions({ action, lead_id?, transaction_id?, fields?, confirm_token? })
action | Required |
|---|---|
create | lead_id, fields.transactionName |
update | lead_id, transaction_id |
update_address | lead_id, transaction_id |
create requires fields.transactionName — the downstream endpoint rejects a blank one with a 400 (TRANSACTION_NAME_BLANK). update is not a true partial patch despite accepting a subset of fields — the same endpoint requires fields.transactionName even when you’re only changing something else, or the call fails. update_address accepts the top-level transaction_id (it’s merged into the body automatically) — fields.transactionId works too if you’d rather set it directly; either way one of them is required, or the call fails clearly instead of reaching a raw 500. fields.transactionType/fields.transactionStatus must match a value configured in the team’s own pipeline — an unmatched value doesn’t error, it silently falls back to the pipeline’s first type/status.There’s no delete action — no such endpoint exists in the real API.