API Endpoint "Events" doesn´t retrieve the fields "Reason" and "CancelledOn" despite being in the model
AnsweredDescription of the Issue:
When running:

…the fields
Stornierungsgrund (EV200_Cancel_Reason)
Storniert von (EV200_Cancel_User_ID)
are not retrieved.
When trying to retrieve the fields "Reason" and "CancelledOn". For cancelled events (for example the events 10489 with the reason "Anderer Grund - sh. Veranstaltungsnotiz Code 31" and 7005 "Agentur hat Pitch verloren, Code 21") its not retrieving the code for the reason and no CancelledOn timestamp, it is just empty and they can´t use it further.
We checked the API Help page and the Info field to these fields suggest that it should retrieve the information they´re looking for. Could you check if that is a bug or if we´re doing something wrong?
Those Events are saved under cancelled and archived events and not in the “active” event area anymore.

As you see in the screenshot the Field has a value but API won't retrieve it.
Client:
MesseStuttgart_PROD_0071404508
Version:
24.22025072501
zendesk:
#383247
-
This one is interesting. I get a 404 error on cancelled events when testing in 26.1 QE.
I don't think this api endpoint works on cancelled/ archived events. I am going to vote it as an enhancement, but will let someone else also comment on this one.
-
I get the same thing as Nicole. I tested in 25.4 and 26.1 and get 404 with both. I think it's probably an enhancement.
-
Seth Halvaksz would you agree to issue as an enhancement or would there be someone worth bringing into this thread?
-

Try checking this checkbox under Event Management Config, then try to fetch the cancelled event again.
Should fix the 404 thing.

I also see both fields we are referencing here, so it does work. -
Following
-
That's interesting that the Show cancelled events checkbox controls what's visible via the API too. I guess it makes logical sense, but I could see a use case where you'd want to pull cancelled events via the API but not see them on your calendars in Enterprise.
-
It's because the API we offer is effectively just a wrapper for our list data classes (aka the engine that powers the grids in the software)
So any features that work for the grids typically work for the API as well unless we went in and manually enhanced it not to at some point.
Please sign in to leave a comment.
Comments
8 comments
Date Votes