# update\_event

Source: <https://telegafirst.com/docs/mcp-tool-update-event>
Locale: ru
releaseGitSha: ea133cd4ad87fe549ef000b139be145be9bd1717
sourceContentDigest: 136177df01d9ad14b867e0dc8aa7fd35398146b2afdedf1453ed8b8663a0f544
Version: 2

# update\_event

Update an event by its \`seqNum\` (a partial patch — send only the fields you change; phase + start/end times are NOT settable here). \`is\_online\` marks an event as online. Also binds the event automation with seq addresses: \`registration\_chain\_seq\_num\`, \`checkin\_chain\_seq\_num\`, \`checkout\_chain\_seq\_num\`, \`post\_event\_chain\_seq\_num\`, \`decline\_chain\_seq\_num\`, \`start\_event\_chain\_seq\_num\`, \`no\_show\_chain\_seq\_num\`, \`reminder\_24h\_chain\_seq\_num\` — each a message-chain seq\_num as a string (send \`null\` to unbind, omit to leave alone). Each binding also accepts an ENTRY STEP — \`registration\_chain\_step\_seq\`, \`checkin\_chain\_step\_seq\`, \`checkout\_chain\_step\_seq\`, \`post\_event\_chain\_step\_seq\`, \`decline\_chain\_step\_seq\`, \`start\_event\_chain\_step\_seq\`, \`no\_show\_chain\_step\_seq\`, \`reminder\_24h\_chain\_step\_seq\` — a step seq\_num of THAT SAME chain, meaning «start the funnel at this step instead of at the beginning». A step is only accepted TOGETHER with its chain in the same call; sending a step without its chain is an error, and sending a chain without a step means «start from the beginning» (which is NOT the same as naming whichever step is first today — the first step can be edited). Plus \`catalog\_ids\` containing tenant Catalog.seq\_num positive int4 decimal strings for ticket tiers (whole list; \`\[]\` unbinds); response \`catalogIds\` carries those same sequence strings, never Catalog primary keys. \`capacity\` may not exceed \`target\_registrations\`. Idempotent. Returns the updated event. Errors NOT\_FOUND if an event or catalog sequence does not exist for your tenant.

## Права и условия

required\_scopes: ALL.

| Поле | Значение |
| - | - |
| description | "Update an event by its \`seqNum\` (a partial patch — send only the fields you change; phase + start/end times are NOT settable here). \`is\_online\` marks an event as online. Also binds the event automation with seq addresses: \`registration\_chain\_seq\_num\`, \`checkin\_chain\_seq\_num\`, \`checkout\_chain\_seq\_num\`, \`post\_event\_chain\_seq\_num\`, \`decline\_chain\_seq\_num\`, \`start\_event\_chain\_seq\_num\`, \`no\_show\_chain\_seq\_num\`, \`reminder\_24h\_chain\_seq\_num\` — each a message-chain seq\_num as a string (send \`null\` to unbind, omit to leave alone). Each binding also accepts an ENTRY STEP — \`registration\_chain\_step\_seq\`, \`checkin\_chain\_step\_seq\`, \`checkout\_chain\_step\_seq\`, \`post\_event\_chain\_step\_seq\`, \`decline\_chain\_step\_seq\`, \`start\_event\_chain\_step\_seq\`, \`no\_show\_chain\_step\_seq\`, \`reminder\_24h\_chain\_step\_seq\` — a step seq\_num of THAT SAME chain, meaning «start the funnel at this step instead of at the beginning». A step is only accepted TOGETHER with its chain in the same call; sending a step without its chain is an error, and sending a chain without a step means «start from the beginning» (which is NOT the same as naming whichever step is first today — the first step can be edited). Plus \`catalog\_ids\` containing tenant Catalog.seq\_num positive int4 decimal strings for ticket tiers (whole list; \`\[]\` unbinds); response \`catalogIds\` carries those same sequence strings, never Catalog primary keys. \`capacity\` may not exceed \`target\_registrations\`. Idempotent. Returns the updated event. Errors NOT\_FOUND if an event or catalog sequence does not exist for your tenant." |
| domain | "events" |
| name | "update\_event" |
| platform\_version | "1.0.20" |
| required\_scopes | \["events:write"] |
| risk | "write" |
| scope | "events:write" |
| title | "Update Event" |

## Входные параметры

[update\_event: inputSchema](https://telegafirst.com/docs/schema-b2f5ea27bae6bbf7b94029840b95d89b183d16816210566531bfb95af3993dc1)

## Результат

null