Update an event with PUT

PUT/org-content/event/{id}

org-content:write update_org_event_with_putDestructiveIdempotentDeprecatedSunset 2027-06-30

Behaves exactly like PATCH /org-content/event/{id}: it changes only the fields sent and returns the event item, so it is not a full replacement. Deprecated: it will be withdrawn on 2027-06-30. Use PATCH /org-content/event/{id}, which the Deprecation and Sunset headers point towards. Needs permission to manage the organisation's content. dry_run shows the result without saving it. It emits the same updated webhook event and favourite notifications as PATCH, and sending the earlier values undoes it, but not the notification.

Path parameters

idstring (uuid)Required#
The item's id.

Query parameters

dry_runboolean#
Validate and run the call without committing it, returning what the real call would return with meta.dry_run set.

Request body

application/json, required · OrgEventUpdate

titlestring#
The title, up to 256 characters.
summarystring | null#
A short summary.
external_linkstring | null#
A link to material held elsewhere, up to 2048 characters.
image_file_keystring | null#
The file key of an image from POST /org-content/images.
bodystring | null#
The body, as HTML.
authorstring | null#
The author as shown to readers, up to 255 characters.
publishedboolean#
Whether readers can see the item. Defaults to true on create.
featuredboolean#
Whether the item is the featured one. Featuring takes the flag from the item that held it. An event that has ended cannot be featured. Defaults to false on create.
publish_datestring | null#
When the item becomes visible to readers. Defaults to the moment it is created.
locationstring | null#
Where the event is held.
start_datestring | null#
When the event starts.
end_datestring | null#
When the event ends, on or after start_date when both are sent.

{
  "title": "Annual meeting, rescheduled"
}

Responses

200

The updated event item.

OrgEvent

{
  "data": {
    "id": "9a9d1c5e-4f2b-4c8e-9a7d-2f1e6b3c4d5a",
    "type": "event",
    "title": "string",
    "summary": "string",
    "body": "string",
    "author": "string",
    "external_link": "string",
    "image_file_key": "string",
    "published": true,
    "featured": true,
    "publish_date": "2026-06-12T10:00:00+00:00",
    "location": "string",
    "start_date": "2026-06-12T10:00:00+00:00",
    "end_date": "2026-06-12T10:00:00+00:00",
    "like_count": 1,
    "comment_count": 1,
    "created_at": "2026-06-12T10:00:00+00:00",
    "updated_at": "2026-06-12T10:00:00+00:00"
  }
}

401

Authentication failed. error.code is one of invalid_token, expired, revoked.

Error

403

Authorization failed. error.code is one of org_disabled, ip_blocked, missing_scope, scope_disabled, user_disabled.

Error

404

Resource not found (error.code = not_found).

Error

422

The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per problem, or a code documented on the operation.

Error

429

Rate limit exceeded (error.code = rate_limited).

Error

Examples

curl -X PUT https://your-org-domain/kong/core/api/v2/org-content/event/{id}\
  -H "Authorization: Bearer $HELM_API_KEY"\
  -H "Content-Type: application/json"\
  -d '{
  "title": "Annual meeting, rescheduled"
}'