Edit Events

Update an Event

Updates an existing event by eventId. You can change the title, schedule, time zone, description, links, button layout, privacy settings, and other details—the same fields supported when creating an event.

Authentication uses an API key issued by Networked.

Not supported on update: changing the recurrence rule (how often the event repeats). See Editing recurring events below.

HTTP Method

PUT

Endpoint

https://api.networked.co/events

Headers

Name	Type	Required	Description
x-api-key	string	Yes	Secret API key provided by Networked. Required for authentication.
spaceId	string	No	If the event belongs to a Space, pass the Space ID. If omitted, the community tied to your API key is used.
Content-Type	string	Yes	`application/json`

Body Parameters

Name	Type	Required	Description
eventId	string	Yes	ID of the event to update (from Create Event or Get Events).
name	string	Yes	Event title. Minimum 3 characters.
description	string	Yes	Event description (plain text or HTML). May be an empty string.
type	number	Yes	Event type. See EventType in Create Event.
eventFormatType	number	Yes	Required for virtual events (`type: 0`). See EventFormatType in Create Event doc.
timezone	object	Yes	Time zone object (`key`, `value`, `timezone`). See Create Event doc.
startTime	number	No	Event start (Unix timestamp in milliseconds).
endTime	number	No	Event end (Unix ms). Must be after `startTime` when both are sent.
richText	string	No	Rich-text editor payload (same format as the Networked UI).
community	string[]	No	Community IDs for collaboration / shared feed.
settings	object[]	No	Privacy and access rules (`questionId`, `scope`, `tagArray`). See Create Event doc.
registrationLink	object[]	No	Up to three labeled external URLs.
websiteLink	object	No	Single labeled website URL.
attachmentLink	object	No	File attachment (`fileId`, `actionName`).
ctaButtonLayout	object	No	Primary / secondary / tertiary button slots. See Create Event doc.
location	string	No	Physical location (In Person events).
contactEmail	string	No	Contact email on the event.
contactNumber	string	No	Contact phone on the event.
eventImage	string	No	File ID for listing image. Send `""` to remove the image.
isHideInterestedGoing	boolean	No	RSVP / Respond: `false` = show, `true` = hide.
isHideAddToCalender	boolean	No	Add to calendar: `false` = show, `true` = hide.
isHideShare	boolean	No	Share: `false` = show, `true` = hide.
hideFromDiscover	boolean	No	If `true`, hidden from Discover on mobile.
recurrenceOption	number	No	Recurring events only. How far edits apply. See Editing recurring events.

Do not send on PUT: recurrenceRule — recurrence patterns are set only at event creation and cannot be changed here.

For full details on dates, time zone, settings, links, and CTA layout, see the Create Event documentation.

Editing recurring events

Use this section when updating an instance that belongs to a recurring series (created with a recurrence rule at post time).

Recurrence rule cannot be changed

Important: After an event is created, its recurrence pattern cannot be updated through this API.
You cannot change Daily / Weekly / Custom settings, end date, occurrence count, or any other recurrenceRule field on PUT.
There is no recurrenceRule property on this endpoint.
To change how an event repeats, delete the series and create a new event with the desired recurrence.

This matches the Networked app: "Recurrence cannot be changed after event creation. Consider deleting and recreating the event."

recurrenceOption — how far your edit applies

When updating a recurring event, send recurrenceOption to choose scope (same choices as Edit recurring event in the app):

Value	UI label	What gets updated
0	This event	Only the event specified by `eventId`. Other occurrences in the series are unchanged.
1	This and following events	This occurrence and all later occurrences in the same series receive the same updates (title, description, links, settings, etc.). Earlier dates are not changed.
2	All events	Every occurrence in the series is updated to match, including past and future dates (except fields handled only on the instance you called).

When to use each value:

Your goal	recurrenceOption
One-off change on a single date	`0` (or omit)
Change this date and all future dates in the series	`1`
Change the entire series	`2`
Event is not recurring	Omit or `0`

Moving to a different calendar day

If you change startTime so the event falls on a different calendar day than before, the API updates only that single event, even when recurrenceOption is 1 or 2.

Series-wide propagation (1 or 2) runs only when:

The event is part of a recurring series, and

The start date stays on the same calendar day (you may still change the time of day), and

recurrenceOption is 1 or 2.

Tip: To shift times across many occurrences on the same dates, keep the same calendar day in startTime and use recurrenceOption 1 or 2.

Sample request (non-recurring event)

{
  "eventId": "6855529c78bddf001282dd01",
  "name": "Updated Community Meetup",
  "description": "Agenda and speakers updated.",
  "type": 0,
  "eventFormatType": 0,
  "timezone": {
    "key": "Asia/Kolkata",
    "value": "(GMT +05:30) India Standard Time",
    "timezone": "IST"
  },
  "startTime": 1746648000000,
  "endTime": 1746651600000,
  "isHideInterestedGoing": false,
  "isHideAddToCalender": false,
  "isHideShare": false
}

Sample request (recurring — this event only)

{
  "eventId": "6855529c78bddf001282dd01",
  "name": "Meetup — March 15 only",
  "description": "Special session for this date.",
  "type": 0,
  "eventFormatType": 0,
  "timezone": {
    "key": "Asia/Kolkata",
    "value": "(GMT +05:30) India Standard Time",
    "timezone": "IST"
  },
  "recurrenceOption": 0
}

Sample request (recurring — this and following events)

Use when the start date remains on the same calendar day as before; only time or other fields change across this and future occurrences.

{
  "eventId": "6855529c78bddf001282dd01",
  "name": "Weekly Meetup (new title)",
  "description": "Updated description for this and future sessions.",
  "type": 0,
  "eventFormatType": 0,
  "timezone": {
    "key": "Asia/Kolkata",
    "value": "(GMT +05:30) India Standard Time",
    "timezone": "IST"
  },
  "startTime": 1746648000000,
  "endTime": 1746651600000,
  "recurrenceOption": 1
}

Sample request (recurring — all events in series)

{
  "eventId": "6855529c78bddf001282dd01",
  "name": "Weekly Meetup (series-wide title)",
  "description": "Applies to every occurrence in the series.",
  "type": 0,
  "eventFormatType": 0,
  "timezone": {
    "key": "Asia/Kolkata",
    "value": "(GMT +05:30) India Standard Time",
    "timezone": "IST"
  },
  "recurrenceOption": 2
}

Sample Response

{
  "data": "Success",
  "error": false,
  "message": "Success"
}

Response Interface

interface UpdateEventResponse {
  data: string;
  error: boolean;
  message: string;
}

Response Field Descriptions

Field	Type	Description
data	string	Success message when the update completes.
error	boolean	`false` indicates the API call was successful.
message	string	Human-readable result of the request.

Reference

Standard Response Codes Reference

Create Event (POST /events) — field definitions, enums, dates, time zone, settings, CTA layout (create-only: recurrenceRule)

Get Events (GET /events) — list events and obtain eventId

Event Recurrence Examples (create) — recurrence payloads apply only to POST; not accepted on PUT

Notes

You need a valid API key for the community that owns the event.

Obtain eventId from Create Event or Get Events before calling PUT.

Do not send recurrenceRule on update; use recurrenceOption for recurring series scope only.

Changing virtual eventFormatType to Huddle or Live may provision a new meeting room (same behavior as create).

CTA hide flags are inverted: false means the button is visible.

Upload files first, then pass file IDs for eventImage or attachmentLink.fileId.

Rate limits apply to API key requests. Retry with backoff if you receive a rate-limit response.

Update an Event

HTTP Method

Endpoint

Headers

Body Parameters

Editing recurring events

Recurrence rule cannot be changed

recurrenceOption — how far your edit applies

Moving to a different calendar day

Sample request (non-recurring event)

Sample request (recurring — this event only)

Sample request (recurring — this and following events)

Sample request (recurring — all events in series)

Sample Response

Response Interface

Response Field Descriptions

Reference

Notes

Request

Responses

Edit Events

Update an Event#

HTTP Method#

Endpoint#

Headers#

Body Parameters#

Editing recurring events#

Recurrence rule cannot be changed#

recurrenceOption — how far your edit applies#

Moving to a different calendar day#

Sample request (non-recurring event)#

Sample request (recurring — this event only)#

Sample request (recurring — this and following events)#

Sample request (recurring — all events in series)#

Sample Response#

Response Interface#

Response Field Descriptions#

Reference#

Notes#

Request

Responses

Update an Event

HTTP Method

Endpoint

Headers

Body Parameters

Editing recurring events

Recurrence rule cannot be changed

recurrenceOption — how far your edit applies

Moving to a different calendar day

Sample request (non-recurring event)

Sample request (recurring — this event only)

Sample request (recurring — this and following events)

Sample request (recurring — all events in series)

Sample Response

Response Interface

Response Field Descriptions

Reference

Notes