Integration Requirements for Event Management

Warning

Deprecation Notice: The Marketing Version 202507 (Marketing July 2025) has been sunset. We recommend that you migrate to the latest versioned APIs to avoid disruptions. For information on all the supported versions, refer to the migrations documentation. If you haven’t yet migrated and have questions, submit a request on the LinkedIn Developer Support Portal.

LinkedIn is in the process of rolling out a Technical Sign Off process for the Event Management program. This ensures that our members get the best experience whether using LinkedIn's native UI or a partner product. The technical review and sign off also ensures that there are no gaps in integrations and that partner products keep up with the latest features and updates released by LinkedIn.

As an API partner, please go through the requirements listed below. These are the capabilities that an integrating partner is expected to build in their product. Plan and incorporate these features early in your design. When you're nearing completion, you must initiate a Technical Sign Off request by contacting your LinkedIn POC on the Business Development team.

A demo will be scheduled during which you'll be asked to showcase all your product capabilities. During this evaluation, LinkedIn can suggest modifications which should be completed for the sign off. If all criteria are met (as per the envisioned scope), the technical sign-off is awarded.

Requirements

Rule	API capabilities to be demonstrated in Demo
	Basics
EM-001	Demonstrate OAuth 2.0 integration with right scopes and consent screen.
EM-002	Demonstrate ability to periodically verify that an access token is valid (heartbeat /me).
EM-003	Demonstrate ability to detect access token expiry.
EM-004	Demonstrate ability to re-trigger OAuth Flow in case token has expired or been invalidated.
EM-005	Demonstrate ability to use refresh tokens to mint new access tokens.
EM-006	Demonstrate ability to detect refresh token expiry and re-trigger OAuth Flow.
	Core
EM-101	Demonstrate ability to retrieve organization's events. Restricted to organizations in which the authenticated member has one of the following company page roles. ADMINISTRATOR, CONTENT_ADMINISTRATOR.
EM-102	Demonstrate ability to modify organization's event. Restricted to organizations in which the authenticated member has one of the following company page roles. ADMINISTRATOR, CONTENT_ADMINISTRATOR.
EM-103	Demonstrate ability to find events by organizer and filter by: EventTimeBasedFilter (lifeCycleState, start / end time) or EventEntryCriteria (GATED or PUBLIC).
EM-104	Demonstrate ability to sort events by START_TIME_ASC or END_TIME_DESC.
	Event Creation
EM-201	Demonstrate ability to create an event of OnlineEventType: LiveVideo.
EM-202	Demonstrate ability to create a test event for OnlineEventType: LiveVideo by setting eventDiscoveryMode to GATED.
EM-203	Demonstrate ability to create an event of OnlineEventType: External.
EM-204	Demonstrate ability to create an event of InPersonEventType.
EM-205	Demonstrate ability to create a background image asset. This involves both 1) registering an upload and 2) uploading a background image. Adding a background image asset to an event is optional, but recommended.
EM-206	Demonstrate ability to add a lead gen form (i.e. event registration form) to an event during event creation. To add a form, specify a Privacy Policy URL to be included in the disclaimer language of the form.
EM-207	Demonstrate ability to post an event on LinkedIn by making a request to the Posts API. An event is readable and writable only if you post it.
EM-208	Demonstrate ability to fetch a newly created event. An event is not fetchable until one posts that event. The last component of the URL path is the ID of the event to fetch.
	Event Management
EM-301	Demonstrate ability to update an event by changing the vanity name of a newly created event. An event is not updatable until you post it.
EM-302	Demonstrate ability to delete an event. An event is not deletable until one posts that event. One deletes a posted event by deleting its associated post. The last component of the URL path is the URL-encoded URN of the post to delete.