# Add a registrant API - documentation/behavior mismatch **URL:** \ **Category:** Meetings\ **Created:** [May 16, 2022, 6:49pm UTC](https://devforum.zoom.us/t/add-a-registrant-api-documentation-behavior-mismatch/69048 "2022-05-16T18:49:34Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![blichtman](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/blichtman/32/37717_2.png) [@blichtman](https://devforum.zoom.us/u/blichtman)\ **Post date:** [May 16, 2022, 6:49pm UTC](https://devforum.zoom.us/t/add-a-registrant-api-documentation-behavior-mismatch/69048/1 "2022-05-16T18:49:34Z")
I’m working on building recovery logic for when our application tries to add a registrant to a meeting without registration enabled. The documentation for the [Add a meeting registrant API](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/meetingRegistrantCreate) seems to state that if the API returns a response with a 404 status code and an error code of 404, then registration is not enabled (actually, the documentation formatting is really off, but I think that’s what it’s claiming). However, the observed behavior is that we get a 400 status code and an error code of 404. What is the intended behavior? If the 400/404 combo is intended, would it be possible to update the documentation to match the actual behavior? Thank you! ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [May 23, 2022, 7:22pm UTC](https://devforum.zoom.us/t/add-a-registrant-api-documentation-behavior-mismatch/69048/2 "2022-05-23T19:22:02Z")
Hi @blichtman Hope you are doing great! Thanks for bringing this to our attention. Allow me to do some testing on my end and I will reach out to the Docs team to address this. Best, Elisa