# Case inconsistency with Emails

**URL:** <https://devforum.zoom.us/t/case-inconsistency-with-emails/96870>\
**Category:** Meetings\
**Created:** [October 16, 2023, 8:02pm UTC](https://devforum.zoom.us/t/case-inconsistency-with-emails/96870 "2023-10-16T20:02:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vsehgal](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vsehgal/32/23835_2.png) [@vsehgal](https://devforum.zoom.us/u/vsehgal)\
**Post date:** [October 16, 2023, 8:02pm UTC](https://devforum.zoom.us/t/case-inconsistency-with-emails/96870/1 "2023-10-16T20:02:35Z")

</div>

### Format Your New Topic as Follows:

**API Endpoint(s) and/or Zoom API Event(s)**  
[_Link the API endpoint(s) and/orZoom API Event(s) you’re working with to help give context._](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/reportMeetingParticipants)

**Description**  
We are trying to lookup an email address against the payload returned on a page. This would let us know if the participant with the mentioned email address attended the meeting.

**Error?**  
We are noticing that the case of the email address is inconsistent when we get the paginated result with next page token vs when its not. This is is throwing off our integration and missing out on counting the participants.

**How To Reproduce**  
_Steps to reproduce the behavior:_  
\*1. Create registrants with camel case email addresses in the meeting and make them as participants.  
\*2. Use the above endpoint to retrieve the participants with page size less than total participants so the next page token is created  
\*3. Then run the above endpoint for your meeting with page size greater than total participants so there is no next page token

You will notice -

1. When there is a next token, all email addresses returned are in lower case
2. When without a next token, all email addresses are returned as the case with which they were created as registrants.

Can you please assist with this as it is getting very difficult to deal with this issue and will need a major and costly design change to the integration if we have to convert each participant instance’s email address to lowercase and then compare them.

This has been reported before [Participant email casing changes based on next\_page\_token presence in response](https://devforum.zoom.us/t/participant-email-casing-changes-based-on-next-page-token-presence-in-response/52274)

---

<div class="post-metadata">

**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:** [October 31, 2023, 8:57pm UTC](https://devforum.zoom.us/t/case-inconsistency-with-emails/96870/4 "2023-10-31T20:57:50Z")

</div>

Hi @vsehgal  
Thanks for reaching out to us  
Are you still seeing this behavior on your end?

I just wanted to confirm that I did some testing on my end and was not able to replicate this on my end. Even if I register the participants using camel case, when I run the report I get the mail with lower cases, no matter if there is a next\_page\_token or not