Hi @Wandel33225 , we currently don’t have an API to create a new Event Type. Right now, the only one we have is one-off which you’ve mentioned does not meet your needs. 

Could you share more information on what Event Type details you would need to pass to create a new ET and generate a single use link? 

Here’s a refined version of your requirements:

• We will programmatically create an EventType on Calendly through our backend APIs.
• The URI of the created EventType will be stored in our database.
• We will set up WebHooks to trigger backend processes whenever a slot is booked for that event.
• The event will span multiple days, and even after a meeting has been scheduled for that event, other participants will still be able to book slots for the same event.
• Need to pass extra details with metadata from our backend api’s for webhooks such that we can process our backend process effectively.

Could you share some way with which we can achieve these requirements.

@Wandel33225 since we don’t have an api to create one-to-one event type, I was wondering if you can still make use of one-off API. However, this may not work because you need this event to be on going, which means a single use link is not enough. 

As for passing information, you could automatically add our standard UTM parameters on the booking page url, which you can then get it back via Webhook. 

We are looking for something that could help create a new one-to-one event type, but I don’t timelines yet. For your use case, are you looking to configure all event type details or just a basic ones such as name, description, duration etc.

We need to configure eventType’s name description, duration and setting unique identifier of our backend resources as metadata in other fields.
And as soon as eventType is created need to store eventType uri or unique identifier on our backend

@Wandel33225 thank you. Soon as we have something, we will reach out to you. Are you open to using the API as beta user once we have it?