Dynamics Community Forum Thread Details

Event API documents, built-in locking, reservation, or hold mechanism for event passes, roadmap

Hi there,
I am currently evaluating the Event API for a new project. After creating a Web Application in Customer Insights - Journeys, I received the following API documentation endpoint:
https://public-can.mkt.dynamics.com/api/v1.0/orgs/<orgid>/eventmanagement/doc/public-api.json
I imported the OpenAPI definition into Swagger Editor for review. However, I found that the documentation is quite limited and does not provide enough detail for implementation purposes.
I would appreciate your guidance on the following questions:

1. Is there more comprehensive documentation available for the Event API?
I was unable to find detailed endpoint descriptions, request/response examples, or usage guidance similar to what is available for Dataverse Web API or other Microsoft APIs.

2. Does the Event API provide any built-in locking, reservation, or hold mechanism for event passes?
Specifically, I would like to understand whether the API includes functionality to prevent the last available pass from being purchased simultaneously by multiple users during the registration process.

3. What is the future roadmap for the Event API?
Since Microsoft retired Outbound Marketing in 2024, I would like to know whether the Event API is considered a strategic, long-term API or whether there are any announced plans for deprecation or replacement.
Thank you very much for your assistance. I appreciate any information, documentation, or guidance you can provide.

Kind regards,

Frank

public-api.json

Categories:

Dynamics 365 Customer Insights - Journeys

These are all valid questions. Based on Microsoft's current public information:
Documentation: The Event API documentation is relatively sparse compared to the Dataverse Web API. Most developers rely on the OpenAPI specification and experimentation because Microsoft has not published comprehensive endpoint documentation.
Concurrency/Reservation: There is no publicly documented built-in reservation or locking mechanism for event passes. If preventing overselling is a business-critical requirement, you should assume you'll need to implement concurrency control in your application unless Microsoft confirms otherwise.
Roadmap: Microsoft has stated that Event Management remains part of Customer Insights Journeys, but they have not publicly published a detailed roadmap specifically for the Event API. Therefore, it's best to obtain confirmation directly from Microsoft through Support or the Dynamics 365 Community if your project depends heavily on these APIs.

Quick Links

Subscribe to this forum!