LinkedIn Events API: endsAt required from 202605, no edits once an event starts

AnnouncedMay 2026

EffectiveMay 2026

PlatformLinkedIn

What changed

The May 2026 release (version 202605) makes endsAt a required field on every event type in /rest/events; create requests without it are rejected, while 202604 and earlier still treat it as optional. The same release adds hasDarkUgc, a create-only flag for off-platform events that exist only behind a sponsored dark post and never appear organically. Earlier, a March 2026 documentation update sorted Event fields into read-only, create-only and updatable, said no field (not even name or description) can be updated after an event has begun, and marked live audio events as deprecated.

What it means

From version 202605, creating a LinkedIn Event without an end time fails. LinkedIn's docs also say an event can't be edited once it has started, and live audio events are deprecated.

Who is affected

Schedulers, event platforms and agencies that create or update LinkedIn Events for Company Pages through the Events Management API.

What to do by May 2026

Always send endsAt when creating events on 202605 or later, make all edits before startsAt, and stop offering live audio events.

What this means for you

Apps that make LinkedIn Events for a company now have to say when the event ends, not just when it starts. Also, once an event has begun, nobody can change it through an app anymore, not even the title. Fix any typos before the start time. Audio-only live events are being phased out.

The details

endsAt required (breaking, version 202605): every event type needs endsAt (epoch milliseconds) on create. Requests without it fail with a validation error. Versions 202604 and earlier still accept a missing endsAt, until they sunset (202604 sunsets April 15, 2027).
hasDarkUgc (version 202605): a CREATE ONLY boolean, default false. When true, the event has no LinkedIn event page and is hidden from all organic surfaces whatever its discoveryMode. It exists for off-platform Event Ads, and its post is a dark post made in the ads workflow, not through normal publishing.
Field mutability (documentation update, March 2026): fields are now labelled READ ONLY, CREATE ONLY or UPDATABLE. Updatable fields include name, description, vanityName, startsAt, backgroundImage, discoveryMode and the type sub-fields endsAt, url, address and venueDetails.
Lifecycle lock: once startsAt has passed, every update returns HTTP 400 ("Event cannot be modified once it has started"). Cancelled events return HTTP 403 on update.
Live audio events: marked as deprecated in the March 2026 documentation update. LinkedIn gives no removal date.
Earlier history: see LinkedIn adds the Events Management API.

What to do next

Business owners: Nothing. Double check an event's details before it starts, because tools can't fix them afterwards.
Marketers and agencies: Agree final event titles and descriptions before the start time and plan audio sessions as video or external events.
Developers: Make endsAt mandatory in your event form, block edits after startsAt in your UI, handle the 400 and 403 lifecycle errors, and drop live audio options.

Follow new entries with the RSS feed. Each platform also has its own feed, for example X or Meta.