Description
Sending JSON to PUT # /meetings/{meetingId}/registrants/status in order to cancel a meeting registration
JSON:
{ “action”: “cancel”, “registrants”: [ { “id”: “############”, “email”: “blah.blah@gmail.com” } ] }
It is returning the proper code that the registrant’s status as been changed
Array
(
[code] => 204
)
However, registrant is still registered when I log in to look!
tommy
(Tommy Gaessler)
2
Hey @broker_assistant,
Can you send me a screenshot of that page with the registrant that did not update?
Thanks,
Tommy
Just got the exact same problems, doing :
POST /meetings/:meetingId/registrants
{“email":"xxx@exemple.com”,“first_name”:“XXXX”,“last_name”:“XXX”}
=> Resp 201 Created
PUT /meetings/{meetingId}/registrants/status
{ “action”: “cancel”, “registrants”: [ { “id”: “############”, “email”: “xxx@example.com" } ] } => Resp 204 No content
then show as approved
PUT /meetings/{meetingId}/registrants/status
{ “action”: “cancel”, “registrants”: [ { “id”: “############”, “email”: “xxx@example.com" } ] } => Resp 204 No content
then still show as approved ==== bad behavior
The meeting is registration mandatory and no manual approval.
Also some precision about the difference between deny and cancel in the api docs would be great.
Thanks,
Téo
tommy
(Tommy Gaessler)
4
Hey @teo.goddet,
Please try waiting around 4 seconds before calling the Update Registrant Status endpoint and see if that works.
See this thread for more info:
Deny means to not allow the user to be in the meeting. Cancel would be the user withdrawing their registration.
Thanks,
Tommy