# API Changelog ## 2024-03-07 * Topic types can now be linked to the exam type ## 2023-09-06 * Added **DELETE evaluation/:id/participants** endpoint ## 2023-05-31 * Added: **calendar/:id/setCreationstatus** endpoint * Added: New status filter to teachers, subjects, groups, generic topic and calendar list endpoints. ## 2023-04-06 * Added: Automatic report generation ## 2023-01-27 ## Changed * Removed name/description from genericTopic->blocks * Added topicType to genericTopic->blocks ## 2023-01-11 ### Added * Generic topic api ### Changed * The way you can add a generic Topic to a calendar has been changed. ## 2022-10-26 ### Added * You can now update a participant in a group with the **PUT /group/:id/participant** api call * **participantUpdateType** param to the **POST /group/:id/participant** api call * **integrations field** to the **group** api calls * You can now create a teacher without an emailaddress ### Fixed * When creating/updating subjects, we now check for duplicate items. It should not be possible to add multiple groups, coordinators, questionSets, topic types of the same id. ## 2022-08-25 ### Added * You can now add **labels** to a participant in the /evaluation/:id/addParticipants api call ## 2022-07-14 ### Added * **tracking-id** header explanation to error page ## 2022-02-24 ### Added * **shouldNotUpdateStartDate** field to the evaluationCalendar. ## 2022-02-10 ### Fixed * Integration in evaluationCalendar create/update api calls were added on the wrong place. ## 2022-01-27 ### Added * Added title field to teachers, draftUsers and users * Added title, firstName, prefix, lastName to field to users ## 2022-01-19 ### Added * Flag to subject/calendar update calls to set overwrite=false. When set to false, topicTypes and teachers will not be removed when submitting new ones. ## 2021-12-16 ### Added * Option to label group participants ## 2021-11-08 ### Added * Endpoint to add new participants to an evaluation ## 2021-10-25 ### Added * **isWorkingStudent** and **isGuestTeacher** properties to the subject create/update api calls ## 2021-10-01 ### Added * useExternalIdForCalendar flag to the **PUT /topic/:id** endPoint * externalId support for the user endpoints ## 2021-09-13 ### Added * Added `integrations` attribute to evaluationCalendar, currently for use with Canvas course announcements. ## 2021-09-09 ### Added * Documentation for `/result` endpoints. Main functions have been covered, more intricate things like label filtering will be documented at a later time. ## 2021-09-02 ### Added * /draftUser/:id/block endpoint to be able to block a user linked to the draftUser. * /user/:id/block endpoint to be able to block a user. * A blocked user is not able to login * A blocked user will not receive notifications in the period the user is blocked * The linked roles and organisations will not be removed ## 2021-08-20 ### Added * It is now possible to add `teacherOptions` to a draftUser. These teacherOptions will also be saved by the teacher when you convert the draftUser to a teacher. You can add the following teacherOptions: * isWorkingStudent (boolean) * isGuestTeacher (boolean). ## ### Added * **hasCalendar** flag to the subject list to be able to only retrieve a list of subjects, linked to at least one calendar item ## 2021-08-16 ### Added * Endpoint to anonymize draftUser and it's linked user/teacher(s) ## 2021-08-11 ### **Added** * added missing query parameters for list users: `includeChildOrganisations` and `role` ## 2021-08-01 ### **Added** * add/delete a topicType from an evaluationCalendar ## 2021-07-29 ### Fixed * Some minor text changes on the subject page ## 2021-07-15 ### Added * **totalParticipants** field to the group list response * Missing fields for the calendar item/list response **(itemLock, workflow\.visibility)** ## 2021-07-07 ### Added * Added: Documentation for adding **linkedOrganisations** when creating/updating subjects. * Added: Documentation for populating linkedOrganisations to the subject list * Fixed: Some minor text changes on the subject page ## 2021-07-05 ### Added * GET /subject/:id/getOrganisationTree. Get a list of all organisations linked to the current topOrganisation. * GET /subject/:id/linkedOrganisations. A list of linked organisations of the subject. When a subject is linked to an organisation, the organisation can view the results of that subject. * POST /subject/:id/linkedOrganisations. Link a subject to one or more organisations. The organisations linked to the subject can view the results of that subject. * It is now possible to add an **importLock** to groups, subjects, teachers and evaluation calendar items. When the importLock is set **true**, the item will be locked on the Evalytics portal. Users (quality managers, coordinators, ..) will not able to modify the items. Only functional admins are able to edit them. * **convertedToUser** flag to the GET /draftUsers api endpoint to filter all draftUsers, converted to user. ## 2021-07-01 ### Added * POST /group/bulkImportParticipants. Bulk import with a CSV file ## 2021-06-30 ### Added * Documentation for strictValidation mode when creating/updating a subject or evaluationCalendar ## 2021-06-22 ### Added * API documentation to get a list of questionSets or a single questionSet ## 2021-06-09 ### Added * API documentation to add a single topicType to a subject * API documentation to delete a single topicType from a subject ## 2021-06-02 ### Added * Example to updateStartDate of the evaluationCalendar (POST /evaluationCalendar/:id/updateStartDate) * EvaluationCalender **GET** list and **GET** item will now also return the creationStartDate. This is the date (in unix timestamp) the calendar is going to create the evaluation. . ## 2021-05-14 ### Added * First version of the api documentation --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://doc.evalytics.nl/api-changelog.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.