API: Easier Event Creation and Registrant Removal Endpoints

A few improvements have been released today regarding the events creation and the registrant removal processes. Here's what's new:

Create event

We've slightly improved the POST /events endpoint so that it now allows you to create an event without having to provide at least one child session relationship object. It means that you can peacefully create your event drafts first and later on add sessions to this event and publish it once you're ready! Here's an example of a JSON payload:

{
  "data": {
    "type": "events",
    "attributes": {
      "owner_id": "UUID",
      "title": "My Awesome Event",
      "slug": "my-awesome-event",
      "status": "draft",
      "everyone_can_speak": false,
      "detailed_registration_page_enabled": true,
      "light_registration_page_enabled": false,
      "description": "<h1>My awesome event!</h1>",
      "recording_enabled": true,
      "recording_public": true,
      "show_in_company_page": true,
      "chat_enabled": true,
      "questions_enabled": true,
      "polls_enabled": true
    }
  }
}

And if it makes sense for you to provide a list of sessions to this event, simply add the following relationship attribute:

{
  "data": {
    "type": "events",
    "attributes": {
      // same as above
    },
    "relationships": {
      "type": "sessions",
      "sessions": [{
        "attributes": {
          "estimated_started_at": "2022-06-25T09:30:00Z",
          "timezone": "America/New_York"
        }
      }]
    }
  }
}

Delete registrant

Prior to this day, the only way to remove a registrant was to use the DELETE /sessions/{id}/people/{id} endpoint that required you to provide the ID of a session registrant (either an external registrant or a team member).

We're now excited to announce that you can now use the DELETE /sessions/{id}/people?filter[email][email protected] endpoint to remove a specific user using an email query filter.

That's it for today — happy coding!