**As** a digitalization enabler
**I want to** download meeting notes via the API as JSON
**so that** I can write scripts to reformat them with my company's CI and send them as e.g. PDF to external partners.

As far as i can sse, there is currently no way to get meetings with the API. I want to retrieve planned meetings, meeting day and participants. Not sure, if this is a "bug" or something for the wish list. I thought the API should be complete at least for the objects which can be added, edited and removed.

Begin of the insertion**Added endpoints**End of the insertion Begin of the deletion ### **Environment**:End of the deletion

Begin of the insertionMeetingsEnd of the insertion Begin of the deletion Your OpenProject Version: **OpenProject 10.3.0**End of the deletion

Begin of the insertion* POST /api/v3/meetings

* PATCH /api/v3/meetings/:id

* DELETE /api/v3/meetings/:id

* GET /api/v3/meetings/schema

* POST /api/v3/meetings/form

* POST /api/v3/meetings/:id/form


Agenda ItemsEnd of the insertion Begin of the deletion Operating System / Browser / Language: Windows 10, Chrome, deEnd of the deletion

Begin of the insertion* GET /api/v3/meetings/:meeting\_id/agenda\_items

* POST /api/v3/meetings/:meeting\_id/agenda\_items

* GET /api/v3/meetings/:meeting\_id/agenda\_items/:id

* PATCH /api/v3/meetings/:meeting\_id/agenda\_items/:id

* DELETE /api/v3/meetings/:meeting\_id/agenda\_items/:id


SectionsEnd of the insertion Begin of the deletion ### **Logs**End of the deletion

Begin of the insertion* GET /api/v3/meetings/:meeting\_id/sections

* POST /api/v3/meetings/:meeting\_id/sections

* GET /api/v3/meetings/:meeting\_id/sections/:id

* PATCH /api/v3/meetings/:meeting\_id/sections/:id

* DELETE /api/v3/meetings/:meeting\_id/sections/:id


Recurring meetingsEnd of the insertion Begin of the deletion \-End of the deletion

Begin of the insertion* GET /api/v3/recurring\_meetings

* POST /api/v3/recurring\_meetings

* GET /api/v3/recurring\_meetings/:id

* PATCH /api/v3/recurring\_meetings/:id

* DELETE /api/v3/recurring\_meetings/:id


To be ableEnd of the insertion Begin of the deletion ### **StepsEnd of the deletion to Begin of the insertionmake use of standard index endpoint, introduce a RecurringMeetingQueryEnd of the insertion Begin of the deletion reproduce:**End of the deletion

Begin of the insertionOccurrences of recurring meetingsEnd of the insertion Begin of the deletion \-End of the deletion

Begin of the insertion* GET /api/v3/recurring\_meetings/:id/occurrences/upcoming — Computed IceCube schedule merged with persisted ScheduledMeetings

* GET /api/v3/recurring\_meetings/:id/occurrences/past — Persisted past occurrences

* GET /api/v3/recurring\_meetings/:id/occurrences/cancelled — Persisted cancelled occurrences

* GET /api/v3/recurring\_meetings/:id/occurrences/open — Persisted instantiated (open) occurrences


To instantiate or cancel a meeting, we do not have a primary key yet (if the occurrence is not opened yet). The non working daysEnd of the insertion Begin of the deletion ### **Actual Behavior**

NoEnd of the deletion API Begin of the insertionuses datesEnd of the insertion Begin of the deletion endpointEnd of the deletion to Begin of the insertionidentify them, so I think it's our best ideaEnd of the insertion Begin of the deletion retrieve Meeting Objects.

### **Expected Behavior**

API endpointEnd of the deletion to Begin of the insertionuse the same.

* End of the insertion Begin of the deletion retrieve Meeting Objects, with all typicial functions like PATCH,End of the deletion POST Begin of the insertion/api/v3/recurring\_meetings/:id/occurrences/:start\_time/init — Instantiate a meeting from the template

* DELETE /api/v3/recurring\_meetings/:id/occurrences/:start\_time — Cancel an occurrenceEnd of the insertion Begin of the deletion etc.End of the deletion